WOFrameworksBaseURL
WOFrameworksBaseURL
- Subject: WOFrameworksBaseURL
- From: Ramsey Gurley <email@hidden>
- Date: Thu, 03 Oct 2013 17:00:54 -0700
WO is me.
I'm trying to deploy a beta version on our live server for limited user testing. It is built off a separate branch with lots of new web server resources. Naturally, I figure I'll just set up the beta app the same as my live app, just under a different name. Then all I should need to do is update my WOFrameworksBaseURL and done.
In theory. I tried adding -WOFrameworksBaseURL to the additional args in Java Monitor. That didn't work. I could see something was adding a second, incorrect version of WOFrameworksBaseURL to the end of sun.java.command in the logs.
After much searching, I found
frameworksBaseURL="/WebObjects/${build.app.name}.woa/Frameworks"
in my build.xml. Who added that? Oh, it's in the default build.xml of every new wonder project.
So I removed that, but my override didn't work. The duplicate override wasn't appearing in sun.java.comand, but it just didn't work. It defaulted to /WebObjects/Frameworks or something instead of using what I put into Monitor.
So I added WOFrameworksBaseURL to the properties file in the app and finally, it works. Sorta.
Now, anything added with ERXResponseRewriter has the correct path, but somehow, paths generated ERXStyleSheet, ERXJavaScript, and ERXFavIcon are still wrong. They use /WebObjects/AppName.woa/Frameworks instead of /WebObjects/AppNameBeta.woa/Frameworks.
Does this sound familiar to anyone?
Ramsey
_______________________________________________
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