SOLVED -> Can't find Application class at launch
SOLVED -> Can't find Application class at launch
- Subject: SOLVED -> Can't find Application class at launch
- From: Allen Cronce <email@hidden>
- Date: Wed, 2 Jun 2004 10:02:38 -0700
Hi all,
It resolve this problem, I went to the Expert View of the target
settings and manually set WOAPPLICATION_CLASS_NAME to include the
package path of the Application class. Now it builds the classpath
correctly and the application runs normally.
Best regards,
--
Allen Cronce
Begin forwarded message:
> From: Allen Cronce <email@hidden>
> Date: June 2, 2004 9:00:55 AM PDT
> To: Jean-Frangois GUILLAUD <email@hidden>
> Cc: WOdev List <email@hidden>,
> email@hidden
> Subject: Re: Can't find Application class at launch
>
> Hi Jeff,
>
> Thanks for your suggestions. What I found was that the classpath for
> my application was incorrect. My Application class is in a package
> (i.e. com.paceap.myapp.Application). But the ApplicationClass in the
> classpath file was set to Application (sans package path). When I
> manually edit the classpath to include the package path for the
> Application, it works.
>
> Unfortunately this is really a band-aid fix. Whenever I do a clean
> build, the classpath ends up wrong again. Somehow the project is
> unaware of the fact that my Application is in a package when it
> creates the classpath file. I've tried removing Application.java from
> the project and adding it back, but that doesn't help.
>
> If I can't figure out why it is that Xcode is not respecting my
> package path when creating the classpath file, I guess I'll have to
> stop using the package path in the java classes. This seems like a
> silly work around considering the fact that we have several other
> applications where all of the classes are in packages and we don't
> have any similar build issues.
>
> Does anyone else have any ideas as to what I can do to get Xcode (1.2)
> to do the right thing? Note that I haven't tried rebuilding my project
> from scratch because, well, that's just plain annoying. It's right up
> there with formating my hard disk and reinstalling Mac OS X as far as
> favorite activities are concerned.
>
> Best regards,
> --
> Allen Cronce
>
> On Jun 2, 2004, at 12:32 AM, Jean-Frangois GUILLAUD wrote:
>
>> Hi Allen,
>>
>> Some ideas:
>>
>> You may check that your classpath is properly defined. See in
>> "YourApp".woa/Contents/"YourPlatform" folder. The classpath text file
>> should start with:
>>
>> <code>
>> # JVM == java
>> # JVMOptions ==
>> # JDB == jdb
>> # JDBOptions ==
>> # ApplicationClass == Application
>> APPROOT/Resources/Java/"YourApplication".jar
>> WOROOT/Library/Frameworks/JavaFoundation.framework/Resources/Java/
>> javafoundation.jar
>> WOROOT/Library/Frameworks/JavaEOControl.framework/Resources/Java/
>> javaeocontrol.jar
>> etc...
>> </code>
>>
>> You could also check that your jar file contains Application.class
>> with:
>>
>> <code>
>> jar tf "YourApplication".jar
>> </code>
>>
>> If not, check if your Application.java file is selected in the
>> Application Server target.
>>
>>
>> If your project is not too big, you could try to create a new one and
>> add your sources. Sometimes that helps...
>>
>> If none of this works, give your body a rest. ;-)
>>
>> Regards.
>>
>> Jeff
>>
>>
>>
>> Allen Cronce a icrit :
>>
>>> Hi all,
>>>
>>> I've got a very basic application that won't start. Here's what's in
>>> the log:
>>>
>>> Can't load Application class, exiting...
>>> java.lang.ClassNotFoundException: Application
>>> at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
>>> at java.security.AccessController.doPrivileged(Native Method)
>>> at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
>>> at
>>> com.webobjects._bootstrap.WOBootstrap.main(WOBootstrap.java:68)
>>>
>>> I had exactly this same error when I first wrote the application. I
>>> shook all the usual dead chickens to try and clear the problem
>>> (clean builds, deleting build folders, manually deleting, rebuilding
>>> and installing our custom frameworks, etc.) None of these attempts
>>> worked.
>>>
>>> Ultimately what made it work was forcing a compile error in
>>> Application.java by removing a required import for one of our
>>> framework classes, fixing the compile error, then rebuilding.
>>> Unfortunately the problem is back and that particular magic spell is
>>> not working now.
>>>
>>> Any suggestions as to how I resolve this problem? Note that I'm not
>>> above smearing my body with chicken blood and chanting if that would
>>> help.
>>>
>>> Best,
>>> --
>>> Allen Cronce
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.