Re: Issues Deploying from WOLips
Re: Issues Deploying from WOLips
- Subject: Re: Issues Deploying from WOLips
- From: Lachlan Deck <email@hidden>
- Date: Mon, 1 Sep 2008 11:37:19 +1000
I'm doing this in a similar way, but like so:
JavaMonitorName/version/App.woa
-DWOApplicationBaseURL=/urlto/version
@override
public void finishInitialisation()
{
...
if
( ERXProperties
.booleanForKeyWithDefault
( "ISHFrameworksBaseURL.relativeToApplicationBaseURL", true ) )
{
String realAppName = NSPathUtilities.lastPathComponent( path() );
NSArray< String > components = new NSArray< String >( new String[] {
realAppName, "Contents", "Frameworks"
} );
String newBaseURL = applicationBaseURL();
for ( Enumeration< String > en = components.objectEnumerator();
en.hasMoreElements(); )
newBaseURL =
NSPathUtilities.stringByAppendingPathComponent( newBaseURL,
en.nextElement() );
ERXProperties.setStringForKey( "WOFrameworksBaseURL", newBaseURL );
setFrameworksBaseURL( newBaseURL );
}
...
}
This allows our deployment dudes to not have to fiddle with numerous
JavaMonitor settings :-)
i.e., 'version' is not a real version but like 'a', 'b', 'c' that we
alternate.
On 30/08/2008, at 2:33 AM, Kieran Kelleher wrote:
Not wanting to start a debate (cos I don't have time today :-) ),
but for revision-named bundles (my-app-001, my-app-002, etc.)
symlinks strategy will not work... and secondly just overwriting
existing resources means that an old version app that is still
running with refuse sessions is now getting new version resources
(images, javascript, css, etc .....). For me I want clean rolling
changes without the gamble of merging new version css, javascript,
etc with old version app ....... and of course, then there is the
problem of the browser caching of old versions when the new version
woa is running ..... with versioned split-embedded bundle the
resources URLs are versioned due to their being different ... for
example with the following embedded WSR url .......
<JavaScript - http___www.smartleadsusa.net_cgi-bin_WebObjects_cheetah.woa_238_wo_5T4I9p0kLb5dqkDHztTMx0_4.0.17.12.13.0.7.1.jpg
>
For me, this is all no trouble since I have a deployment script that
I run and everything gets built and deployed to the woa-app servers
while I have about 1 cup of coffee after which I then log in to
WOMonitor and launch new version instances and refuse sessions on
the old version instances.
On Aug 29, 2008, at 12:08 PM, Guido Neitzer wrote:
On Fri, Aug 29, 2008 at 10:02 AM, Kieran Kelleher <email@hidden
> wrote:
This looks interesting, though the WSR are not really an issue
for me.
True for Java Client people like yourself, but for the web app
developer it
is necessary.
Why? I never bother with that. I have my WSRs in a separate project
or in a separate folder and deploy them with rsync within the
deployment script.
Or you do a first time deploy and add some symlinks to the webserver
resources in your application.
You don't have to worry about that, it all depends on your project
layout and and how you do deployments.
cug
_______________________________________________
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
with regards,
--
Lachlan Deck
_______________________________________________
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