I believe WOFrameworksBaseURL and WOApplicationBaseURL are used for
that.
If you are on WO 5.4.3 then those too are broken and I put this in my
application constructor to make them work:
public Application() {
super();
// WOFrameworksBaseURL and WOApplicationBaseURL properties are
broken in 5.4.
// This is the workaround.
frameworksBaseURL();
applicationBaseURL();
if (System.getProperty("WOFrameworksBaseURL") != null) {
setFrameworksBaseURL(System.getProperty("WOFrameworksBaseURL"));
}
if (System.getProperty("WOApplicationBaseURL") != null) {
setApplicationBaseURL(System.getProperty("WOApplicationBaseURL"));
}
}
On Jun 26, 2009, at 9:56 AM, Mr. Frank Cobia wrote:
I am building my application with the frameworks embedded so that I
do not have to worry about different versions of the frameworks for
different apps. I have checked and the build does put the
WebServerResources inside the application's WebServerResources.
However, when accessing the app it builds URLs that refer to the
framework resources as if they were standalone and not embedded.
Is there something I can do to force URLs to be generated that refer
to the resources inside the app instead?
Thanks,
Frank Cobia
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/rparada
%40mac.com
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
