Re: embedded frameworks + split install
Re: embedded frameworks + split install
- Subject: Re: embedded frameworks + split install
- From: Peter Vandoros <email@hidden>
- Date: Mon, 04 Dec 2006 10:00:05 +1100
Hi Ulrich,
I must be missing something very obvious :(.
If you specify the -WOFrameworksBaseURL to point to your embedded
frameworks and then you use some WebServer resources from within the
JavaWOExtensions framework, what would the url be for that resource and
how will the web server know how to find it so it can serve it back to
the user?
I imagine that if i set the -WOFrameworksBaseURL to
"/WebObjects/Applications/YourApp.woa/Contents/Frameworks" and then want
to use a web server resource from the JavaWOExtensions framework, the
URL would look like
"/WebObjects/Applications/YourApp.woa/Contents/Frameworks/JavaWOExtensions.framework/Resources/some_file.gif"
instead of
"/WebObjects/Frameworks/JavaWOExtensions.framework/Resources/some_file.gif".
Am i missing something really obvious here?
thanks
Peter
Ulrich Köster wrote:
Moin Peter,
sorry for the delay.
Am 16.11.2006 um 01:14 schrieb Peter Vandoros:
Ulrich Köster wrote:
Am 15.11.2006 um 01:38 schrieb Peter Vandoros:
Hi Mike,
Doesn't this mean that you will no longer be able to use any of the
WebServerResources from within standard WO frameworks such as
JavaWOExtensions?
No.
Then how would you use a resource in the JavaWOExtensions framework?
What will the url look like? Won't it look something like
"WebObjects/Frameworks/JavaWOExtensions.framework/WebServerResources/some_image.jpg"
As before no need to change you code or components.
What i have been doing to overcome this situation is to create a
virtual directory/symbolic link in the default
/WebObjects/Frameworks directory that points to the framework that
has WebServerResources.
Eg. /WebObjects/Frameworks/my_framework.framework where
"my_framework.framework" points to
"/WebObjects/Applications/YourApp.woa/Contents/Frameworks/my_framework.framework".
This obviously means an extra step in deploying new versions of the
same framework on the same server. It does also mean that if you
have only one valid version of the framework on the server then you
only need to perform this step at time of configuring the server.
The problem is that we're not deploying versions. It's just a bunch
of files moved to the server.
I'm not sure what you mean? Don't you need web access to particular
versions of the Ajax framework?
For sure. Exactly the one that I've used to test the app.
Uli
Peter
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden