On Sep 10, 2008, at 5:00 PM, Mike Schrag wrote:
The app runs normally in development mode. The only "big" change
I've made is to the nightly build of WOLips with the New Hotness.
Yikes. There is a reason this is on nightly and really loudly
stated as "THIS SHOULD BE CONSIDERED UNSTABLE" ... So I would take
the quotes off of "big" :)
I too like to live dangerously. :-)
New Hotness is mostly about classpath changes, so the first thing I
would compare with the old app is the classpath file.
The first thing I do when my app doesn't start is run it from
commandline. Monitor/taskd just muddy the waters here. Go run
your ./YourApp script in the woa and get some REAL console output.
And also what Chuck said :) Check that your classpath file is right
and check that your embedded frameworks are where you expect them to
be.
It doesn't appear that classpath issues are the problem but I did
notice that this item was not in the path for this deployment:
LOCALROOT/Library/Frameworks/JavaWOExtensions.framework/Resources/Java/
JavaWOExtensions.jar
I think I'm looking at the right file -- app.woa/Contents/UNIX/
UNIXClassPath.txt
The only other thing that was different was the ordering off the items
but in further testing by launching from the command line this doesn't
seem to be an issue in this app.
-----
Timothy Worman
Programmer/Analyst - Database Administrator
Graduate School of Education and Information Studies
University of California Los Angeles
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
