Re: Deploying Multiple Versions (and on Windows)
Re: Deploying Multiple Versions (and on Windows)
- Subject: Re: Deploying Multiple Versions (and on Windows)
- From: Ashley Aitken <email@hidden>
- Date: Tue, 27 Apr 2004 14:36:34 +0800
Hi Chuck,
Thanks for your email.
On 27/04/2004, at 12:41 AM, Chuck Hill wrote:
This is completely doable. First off, do NOT rename the project.
That is the wrong path. Just put version 2 in a different directory,
point JavaMonitor at it, and give it a different name in JavaMonitor.
The name that JM uses, the name that appears in the URL, has *nothing*
to do with the name of the project.woa directory. You can name it
ScoobyDo if you want to. This name is only used to resolve to a port
number.
Hey, doesn't anyone read my postscripts (PS) ;-) No need to answer
that. I did realise that the application folder name could be changed,
but thanks for explaining why. I did change the folder than holds the
application, but not the project name (demons be there!).
For frameworks you have a couple of options. The first option you
want to discard is the Apple way of putting them in
/Library/Frameworks/. The versioning stuff might sort of work on OS
X, but not on Windows.
I am sorry, I am not sure of the relationship between putting them in
/Library/Frameworks and the Framework versioning that Apple supplies
(ie folder links inside the Framework.framework folder). Is it the
case that this versioning is only done for frameworks inside the
.../Library/Frameworks directory? Does this versioning work on Windows
at all, even if you use ProjectBuilderWO for development?
Just reject all that crap and do it the Java way:
Careful, some people may get upset ;-) Even I think the versioning
idea is conceptually good.
In side the .woa bundle are classpath files for the various OS's in
appropriately named directories. Install the framework where ever you
want and edit the classpath file to point to where you have installed
it. Done.
Ok, that is what I did, and as you say, it worked. It is the
CLSSPATH.txt file in the Windows directory.
Lately I've taken to bundling the frameworks into the .woa file. I
put then under Contents/Library/Frameworks. Then edit the classpath
files (sed works well for this) and change the path from LOCALROOT/ to
APPROOT/. There you have it - a version safe, single bundle install.
Life is good.
Sounds like a good idea (for some frameworks).
Could you please finish off the solution, with words of wisdom about
the WebServer split deployment?
As I mentioned, I installed the Application's WebServer split on the
WebServer and renamed it (Appv2) and somehow, I think, the application
found it. However, looking at the source for pages in the application
it looks like it was looking for Appv1/...
How does one version the files on the WebServer (if that is needed)?
Cheers,
Ashley.
--
Ashley Aitken
Perth, Western Australia
mrhatken at mac dot com
_______________________________________________
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.