Check this out...
public Application() {
NSLog.out.appendln("Welcome to " + name() + " !");
NSLog.out.appendln("before setting frameworksBaseURL(): " +
frameworksBaseURL());
setFrameworksBaseURL("/WebObjects/myapp.woa/Frameworks");
NSLog.out.appendln("after setting frameworksBaseURL()" +
frameworksBaseURL());
}Outputs /Library/WebObjects/Logs/myapp-instanceJul 27 00:07:04 myapp[2004] (ERXNSLogLog4jBridge.java:40) INFO NSLog - Welcome to myapp ! Jul 27 00:07:04 myapp[2004] (ERXNSLogLog4jBridge.java:40) INFO NSLog - before setting frameworksBaseURL(): /WebObjects/Frameworks Jul 27 00:07:04 myapp[2004] (ERXNSLogLog4jBridge.java:40) INFO NSLog - after setting frameworksBaseURL()/WebObjects/myapp.woa/Frameworks
outputs to apache's access_log127.0.0.1 - - [27/Jul/2008:00:07:50 -0400] "GET /WebObjects/Frameworks/ ERExtensions.framework/WebServerResources/s.gif HTTP/1.1" 404 267
...127.0.0.1 - - [27/Jul/2008:00:09:09 -0400] "GET /WebObjects/myapp.woa/ Frameworks/ERExtensions.framework/WebServerResources/s.gif HTTP/1.1" 200 67
...127.0.0.1 - - [27/Jul/2008:00:15:14 -0400] "GET /WebObjects/myapp.woa/ Frameworks/ERExtensions.framework/WebServerResources/s.gif HTTP/1.1" 304 -
How lame is that? Oh well, at least it works... at the moment.I think maybe that first 404 is Safari reading something bad from it's page cache and using the bad link. I'm guessing this because watching the access log on the first instance a few times it gives the above. On loading the second instance a couple of times, it gives lines 1 and then 3, on the third new instance, repeated loads gave no line at all for s.gif. I assume this means Safari's reading it from the cache. Anyway, how could the launch script contain WOFrameworksBaseURL yet the command fail to set it?? I dropped the command on an open terminal window and got the same before/after output. If nobody but ME is having a problem with this, then it must be getting unset somewhere or something is causing it to be ignored...
Does anyone have any ideas on what I could be doing differently to cause this?
rg On Jul 26, 2008, at 11:47 AM, Rams wrote:
Hi Kieran, On Jul 26, 2008, at 9:39 AM, Kieran Kelleher wrote:Correct me if I am wrong here, but....1) If you are using the embedded frameworks strategy, why are you setting -WOFrameworksBaseURL argument in WOMonitor? You don't need it.Because it wasn't working without it :-)The "embed" feature already has this set on the command line at the end of the launch script.... if anything that is just going to override whatever you set for this in WOMonitor IIRC.That's the part I don't understand. It's set by the build script, but it's still going to /WebObjects/Frameworks instead. That's the only reason I tried setting it in the additional arguments. I have now removed all additional arguments in monitor and everything else seems to be working fine.2) Why is WODirectConnectEnabled true .... for deployment that should be WODirectConnectEnabled false ? IIRC the ResourceManager logic behaves differently when direct connect is enabled. That may be the reason URLs are not correct. Change that to false and see what happens.I inserted it for testing. I was having lots of trouble with the http adaptor returning "No Instance Available" pages, kCFErrorDomainCFNetwork in Safari, and unrendered pages of source in Firefox, so I set direct connect to true so that I could verify that the app half of the equation was working at least.I've removed the direct connect argument and clicking the host:port link in monitor still works. Do I need to set that to false in monitor's additional args explicitly? It seems it was false by default at one time, but that doesn't appear to be the case now.So we can see what the real WOFrameworksBaseURL is, can you open the launch script in text editor, go to the end and copy/paste the line from that generated script that launches and email it to the list?# # Launch the application. # echo Launching ${SCRIPT_NAME}.woa ...echo ${JAVA_EXECUTABLE} ${JAVA_EXECUTABLE_ARGS} -classpath WOBootstrap.jar com.webobjects._bootstrap.WOBootstrap $ {COMMAND_LINE_ARGS} -WOFrameworksBaseURL /WebObjects/myapp-rev-1.woa/ Frameworks eval exec ${JAVA_EXECUTABLE} ${JAVA_EXECUTABLE_ARGS} -classpath WOBootstrap.jar com.webobjects._bootstrap.WOBootstrap $ {COMMAND_LINE_ARGS} -WOFrameworksBaseURL /WebObjects/myapp-rev-1.woa/ FrameworksOn Jul 25, 2008, at 3:56 PM, Rams wrote:The additional arguments listed in my app's config are:-WOFrameworksBaseURL /WebObjects/myapp.woa/Frameworks - WOStatisticsPassword password -WOHost my.domain.com -WOAdaptorURL http://my.domain.com/cgi-bin/WebObjects -WODirectConnectEnabled trueI had WOFrameworksBaseURL on the end but I just moved it to the beginning and pushed it to my instances... with no effect. The adaptor is still trying to pull framework resources from the wrong path. Regardless, it should still be set by the build script, no? I wouldn't think I would need to explicitly set it after that...rg On Jul 25, 2008, at 3:16 PM, Kieran Kelleher wrote:What are your WOMonitor arguments? They are probably formatted incorrectly resulting in the launch command not getting the WOFrameworksBaseURL argument at all since it is *after* the WOMonitor args in the launch script inside the WOA (it is at end of the launch script, see for yourself). I have seen this before, and that was the cause. Also no "\n" in the WOMonitor args text area ... that may cause problem too.HTH, Kieran On Jul 25, 2008, at 2:23 PM, Rams wrote:Hi all, I read http://wiki.objectstyle.org/confluence/display/WOL/Web+Server+Resources+with+Embedded+Frameworks I'm using the build script found here: http://wiki.objectstyle.org/confluence/display/WOL/Alternative+Ant+Build+Script+for+Fully+Embedded+and+Split+Install+BundlesWhich declares WOFrameworksBaseURL in the script. I also tried to explicitly declare it in the additional arguments of the app with no luck. In my apache access_log, I'm still getting:"GET /WebObjects/Frameworks/Ajax.framework/WebServerResources/ dragdrop.js HTTP/1.1" 404 265Obviously, this isn't a problem with direct connect, but I'm wondering why it isn't working. I can't just move the frameworks there, because I don't want to overwrite the installed WO 5.4.2 frameworks. (With wonder's JavaWebObjects.Framework for instance) Does anyone know how I can fix this??Thanks everyone, rg _______________________________________________ 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/kieran_lists%40mac.com This email sent to [EMAIL PROTECTED]_______________________________________________ Do not post admin requests to the list. They will be ignored.Webobjects-deploy mailing list (Webobjects- [EMAIL PROTECTED])Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/rgurley%40mac.com This email sent to [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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]
