D Tim Cummings wrote :
[...]
I embed WebObjects 5.3.3 by modifying the build.xml script created by
wolips when I created my project. I set embed to true in the three
cases. The last one is the one that embeds WebObjects 5.3.3
[...]
So the class end in the application jar ?
On deployment
environment is your app running with java 1.4.2 ?
I am compiling for Java 1.5 so I am pretty sure it is using the Java
1.5 JVM, otherwise it wouldn't ever get started.
I was asking that cause the official JVM for WO 5.3 is 1.4.2, even if
there is not known problems 5.3 isn't qualified with 1.5.
So it may not be the problem there.
(you can compil using 1.5 and targeting 1.4)
Do you try ./app -WODebuggingEnabled NO -WOPort 1234 on you development
box ?
I just tried it then and the app started fine on my development box.
I consider WOBootstrap as class loader (it load woAppClass) and as a
class path maker.
As it run first when lauching your app it built a "generated classpath"
which in turn is used to find class and load them by the JVM. So if in
that generated classpath you have 5.4 jar the class they have may be
loaded instead of the the one you embed.
Switch back to 5.3 for checking if it is the case.
Aurélien
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
