On Apr 2, 2007, at 1:08 PM, Chuck Hill wrote:
On Apr 2, 2007, at 6:50 AM, Greg Brown wrote:
I am running ( trying) Myapp.woa with apache 1.3, Mac OSX 10.4.8 and the documentation doesn't appear to be right! or I misunderstand, so for the record:
Documents say: However, most web applications contain web server resources, such as images. You should place these resources in the web server’s Document Root directory. You accomplish that by performing a split installation.
If I use https to access Myapp.woa, then it seems a split install is necessary. Is that manditory? a split install? if so maybe it should say: "You MUST
What are you seeing that makes you think that?
Here is a snippet from apache access log: 172.214.237.168 - - [02/Apr/2007:14:25:07 -0400] "GET /cgi-bin/WebObjects/Test HTTP/1.1" 200 2804 172.214.237.168 - - [02/Apr/2007:14:25:07 -0400] "GET /WebObjects/Frameworks/JavaDirectToWeb.framework/WebServerResources/Background.gif HTTP/1.1" 200 257 172.214.237.168 - - [02/Apr/2007:14:25:07 -0400] "GET /WebObjects/nucptdb.woa/Contents/WebServerResources/vasealwhite.jpg HTTP/1.1" 404 3752 172.214.237.168 - - [02/Apr/2007:14:25:07 -0400] "GET /WebObjects/Frameworks/JavaDirectToWeb.framework/WebServerResources/LoginMetalBtn.gif HTTP/1.1" 200 1721
As you can see, I used "Test" in the Monitor Application pane, to refer to a nucptdb.woa application. The 3rd line above refers to a nucptdb.woa/Contents/WebServerResources/vasealwhite.jpg, which does exist in the application bundle, nucptdb.woa, but not in the WebServer Document root.
Now in the apache error.log: [Mon Apr 2 14:25:07 2007] [error] [client 172.214.237.168] File does not exist: /Library/WebServer/Documents/WebObjects/nucptdb.woa/Contents/WebServerResources/vasealwhite.jpg
And no jpg vended. To me it seems like apache is looking in the Document root, and I can make things work by putting that jpg in the root.
place these resources in the web server’s Document Root directory.....
A second misunderstanding/documentaion question:
It says (on the Application tab) that when configuring an application one could use any name they wanted for the application's name in the Monitor program, e.g., for Myapp.woa I could call it application Test, then give the path to Myapp.woa/Myapp. Well of course that doesn't appear to work with https! With https the Test app will look for resources in Test.woa, which does not exist. The only way I could get this to work was ignore the documentation and have the Monitor application name match exactly the Myapp.woa name.
Are these realities localized to just my machine? or should the documentation be changed?
You have done / are doing something wrong or not doing something that needs to be done. Or something... :-) We use https and names in monitor that differ from the app name file system all the time with no problems at all. What exactly are you doing / trying to do and what are you seeing? Are you perhaps running in Direct Connect mode (URL like http://some.domain.com:3456/...). Direct Connect (besides being evil and a toy) does not support HTTPS.
Chuck
--
I can make things work by putting /WebObjects/nucptdb.woa/Contents/WebServerResources/vasealwhite.jpg in apache's document root, but that seems like a split install. I used WOlips, and don't have the parameter - wsDestDir(Destination directory where WebServerResorces should be copied during split install (presense of this parameter will trigger split install). WebServerResources will be created under [wsDestDir]/WebObjects/AppName.woa/Contents/.)
set up. On Monitor's Site pane, I have the URL to the WebObjects HTTP adaptor as https://.... and most applications probably have http://.... Could that be a problem?
Thanks for looking, |