I have been messing with 5.4 this morning and have run into an issue when doing a test deployment that I am hoping is just something stupid on my part.
I have built the HelloWorld app that comes with WO 5.4 using 'ant woa', tarred up the woa bundle from dist and untarred it to /Library/WebObjects/Applications/HelloWorld.woa
In all the cases below I am testing using direct connect, not through apache.
If I launch the app manually with no args it works fine. However, if I launch the app with -WOCachingEnabled YES (like you would in deployment) the app starts but fails to render any content, and throws the following error:
The same thing occurs when deploying with JavaMonitor/wotaskd, with caching on, the app doesn't work, with it off it runs fine. (again, using direct connect to test the app)
If I launch the app from /Developer/Examples/JavaWebObjects/HelloWorld/dist/legacy/HelloWorld.woa with caching turned on it works, but prints this in the output log:
Application project found: Will locate resources in '/Developer/Examples/JavaWebObjects/HelloWorld' rather than '/Developer/Examples/JavaWebObjects/HelloWorld/dist/legacy/HelloWorld.woa' .
What am I missing?
--
Seeya...Q
Gold Coast, QLD, Australia (GMT+10)
Ph: +61 419 729 806