RE: [webobjects-newbies] Forcing graphics to load from application server?
RE: [webobjects-newbies] Forcing graphics to load from application server?
- Subject: RE: [webobjects-newbies] Forcing graphics to load from application server?
- From: "Jonathan Fleming" <email@hidden>
- Date: Fri, 11 Jun 2004 11:59:07 +0100
From: Cesare Ferrari <email@hidden>
Reply-To: email@hidden
To: email@hidden
Subject: [webobjects-newbies] Forcing graphics to load from application
server?
Date: Fri, 11 Jun 2004 08:49:23 +0100
Here's the scenario. I've got a live WebObjects application, and have
built an update which i'm wanting to release to our beta testers. Now
the update includes layout/graphics changes, but no DB changes, so I
can run it concurrently with the existing deployment on the same
server.
So, i'm planning on setting up a new WO Application on the server, with
a new name, pointing at the new app. All's well and good, except that
since this is a deployment build, the split install graphics is getting
pulled from the old application (since the path resolves to
/WebObjects/AppName.woa/Contents/WebServerResources/... where AppName
is the build name of the application, not the deployed name. Since
there are clashes in the names of some graphics between the old and new
application, I can't just drop the updated graphics onto the Web
Server.
So, how do I resolve this?
I don't really see your problem... if you have created a new app under a new
name why can't you simply put your updated graphics/layouts in the
Web-Server-Resouces of the new app as well as a copy of any existing
graphics/layouts that are not being changed from the old app? When you build
a split install all the graphics here will be associated with this app only
(unless you have images in the Web-Server-Resouces of a frameworks) and now
you should have no problem.
However, if you have made a copy of the old app make sure you do a clean to
throw out any cached files that might be linking to the old app.
Other than that, i'm probably not understanding your problem well enough.
Jonathan :^)
My thoughts are:
1) Rename the WO Project, and build a deployment build with a different
project name - this will hopefully then give a different path on the
Web Server, so I can deploy the images to a different directory.
2) Force the build to pull the graphics from the Application server -
anyone know how to do this? Is there by any chance a runtime argument I
can use on the App server to force this?
3) Specify an argument on the App Server which changes the name of the
application? Does such a thing exist?
4) Install a development build - will this mean that the graphics are
pulled from the application server? Are there any other differences to
consider?
I'm sure someone out there in WO land has had to deal with this.
Many thanks,
Cesare
_________________________________________________________________
Express yourself with cool new emoticons http://www.msn.co.uk/specials/myemo
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.