Re: embedded frameworks + split install
Re: embedded frameworks + split install
- Subject: Re: embedded frameworks + split install
- From: Peter Vandoros <email@hidden>
- Date: Tue, 05 Dec 2006 10:04:01 +1100
Hi Ulrich,
Thanks for that explanation. It helped a lot.
I didn't realise that you were copying the web server resources part of
the JavaWOExtensions.framework into your app bundle. It makes a lot more
sense now.
thanks
Peter
Ulrich Köster wrote:
Moin Peter,
ALL frameworks and their webserverresources are embedded. The
YourApp-1.0.0-webserverresources.tar.gz is a collection of the
webserverresources from the app and all frameworks. The
WebServerResources from the javawoextensions framework are under
/WebObjects/Applications/AppName-Version.woa/Contents/Frameworks/JavaWOExtensions.framework/WebServerResources/
Apps for 5.2.*, 5.3.* and hopefully 6.0.* can live side by side one
one server.
The app name includes a version string. 'some_file.gif' could differ
if 'YourApp' version 1.0.0 has webobjects 5.2.1 as an dependency where
1.0.1 has webobjects 5.2.2 as an dependency. Or app one uses
JavaWOExtensions from apple and the other from project wonder.....
/WebObjects/Applications/YourApp-1.0.0.woa/Contents/Frameworks/JavaWOExtensions.framework/WebServerResources/some_file.gif
/WebObjects/Applications/YourApp-1.0.1.woa/Contents/Frameworks/JavaWOExtensions.framework/WebServerResources/some_file.gif
/WebObjects/Applications/AnotherCoolWebApp-1.0.0.woa/Contents/Frameworks/JavaWOExtensions.framework/WebServerResources/some_file.gif
If you're running a lot of different apps on one machine you're
wasting some space on the hd. Some mb on a 250gb drive.
Uli
Am 04.12.2006 um 00:00 schrieb Peter Vandoros:
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
_______________________________________________
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