Apple

NSBundle bundle = NSBundle.mainBundle();

System.out.println( "Using NSBundle " + bundle.name() + " on path " + bundle.bundlePathURL() );

for( NSBundle fbundle : NSBundle.frameworkBundles() ) {

System.out.println( "Using Framework NSBundle " + fbundle.name() + " on path " + fbundle.bundlePathURL() );

}

which produces the following output:

Using NSBundle MyApp on path file:/Users/maik/src/git/Foo/MyApp/build/MyApp.woa

Using Framework NSBundle JavaEOAccess on path file:/System/Library/Frameworks/JavaEOAccess.framework

Using Framework NSBundle JavaEOControl on path file:/System/Library/Frameworks/JavaEOControl.framework

Using Framework NSBundle JavaFoundation on path file:/System/Library/Frameworks/JavaFoundation.framework

Using Framework NSBundle JavaJDBCAdaptor on path file:/System/Library/Frameworks/JavaJDBCAdaptor.framework

Using Framework NSBundle JavaWebObjects on path file:/System/Library/Frameworks/JavaWebObjects.framework

Using Framework NSBundle JavaXML on path file:/System/Library/Frameworks/JavaXML.framework

Using Framework NSBundle JavaEOProject on path file:/System/Library/Frameworks/JavaEOProject.framework

Using Framework NSBundle JavaWOJSPServlet on path file:/System/Library/Frameworks/JavaWOJSPServlet.framework

Maik

Am 10.07.2014 um 19:31 schrieb Chuck Hill <email@hidden>:

NSBundle uses the current working directory as a base to locate the bundles. That is one thing to check. For frameworks, I think this needs to be My.framework/Resources/Java

Chuck

On 2014-07-09, 11:49 PM, "Musall Maik" wrote:

Hi,

thanks for the suggestion. Turns out that none of my frameworks are loaded. NSBundle.frameworkBundles() contains only the basic Java… bundles, nothing else. Any idea?

Maik

Am 09.07.2014 um 22:40 schrieb Markus Stoll, junidas GmbH <email@hidden>:

Hi,

I use

NSBundle.bundleForClass(myclass.class).pathURLForResourcePath(_resource);

when I need things to work from unit tests, too

hope this helps, Markus

Am 09.07.2014 um 18:56 schrieb Musall Maik <email@hidden>:

Oh, sorry for not making that clear.

It's involved in that everything works for the running application, but not from within unit tests. The effect that the pathURLForResourceNamed() call returns null happens only in unit tests.

Maik

Am 09.07.2014 um 18:11 schrieb John Huss <email@hidden>:

Sorry, how is WOUnit involved?

On Wed, Jul 9, 2014 at 10:09 AM, Musall Maik <email@hidden> wrote:

Hi,

I have an application that uses a few custom frameworks. When I use

WOResourceManager resourceManager = WOApplication.application().resourceManager();

URL url = "" "foo.dat", null, null );

from within the main application, I get a proper URL to my resource file. But when I use

WOResourceManager resourceManager = WOApplication.application().resourceManager();

URL url = "" "bar.dat", "MyFramework", null );

with the second parameter (framework name) given, I only get back null. Regardless of whether

this is called from within the main application or from the framework's code itself.

Does anybody have a hint for me?

Thanks

Maik

_______________________________________________

Do not post admin requests to the list. They will be ignored.

Webobjects-dev mailing list (email@hidden)

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

_______________________________________________

Do not post admin requests to the list. They will be ignored.

Webobjects-dev mailing list (email@hidden)

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

--

Dr. Markus Stoll (Geschäftsführer)

email@hidden

junidas GmbH, Aixheimer Str. 12, 70619 Stuttgart

Tel. +49 (711) 4599799-11, Fax +49 (711) 4599799-10

Geschäftsführer: Dr. Markus Stoll, Matthias Zepf

Amtsgericht Stuttgart, HRB 21939

References:
	>Re: Accessing a framework's resources in WOUnit tests (From: John Huss <email@hidden>)
	>Re: Accessing a framework's resources in WOUnit tests (From: Musall Maik <email@hidden>)
	>Re: Accessing a framework's resources in WOUnit tests (From: Chuck Hill <email@hidden>)