| WO 5.3.3 works as expected. WO 5.4.3 has a bug. You need to actually set the property in app constructor as a workaround in WO 5.4.3
I still use WO 5.3.3, so I am sorry, I did not think of mentioning this. Do this (stuff in red font) in your app constructor (or your reusable app .......
public WKApplication() { super(); // we use the DA request handler instead of the component request handler // by default. setDefaultRequestHandler(requestHandlerForKey(directActionRequestHandlerKey()));
// Fix for WO 5.4.3 Bug : radar 6487590 System.out.println("WKApplication.WKApplication(): WO 5.4.3 bug - fixing WOFrameworksBaseURL"); frameworksBaseURL(); if ( System.getProperty("WOFrameworksBaseURL") != null ) setFrameworksBaseURL(System.getProperty("WOFrameworksBaseURL"));
// Java 5 Update 4 changed tmp dir. I am changing it back: System.setProperty("java.io.tmpdir", "/tmp/"); // Configure Houdah Qualifier support setupHoudahQualifierSupport();
}
On Jul 13, 2009, at 2:53 PM, George Domurot wrote: So... the 'correct' way of specifying the frameworks directory is via a launch argument, not from within the build.properties file? -G On Jul 13, 2009, at 10:57 AM, Mike Schrag wrote: Also, if you're using 5.4.x and not using the latest Wonder, you are going to have the WOFrameworksBaseURL bug where it isn't set from the -D param.
ms
On Jul 13, 2009, at 1:54 PM, Kieran Kelleher wrote:
Try opening the actual launch script inside the app. At the end of the file is the launch command and u should see the WOFrameWorksBaseURL argument there.
I have seen your problem when other launch args were not specified correctly in WOMonitor causing subsequent launch args, including WOFrameworksBaseURL, not to be set.
For WOMonitor, I find the -D format to work best, for example:
-Duser.name=deploy -DWODirectConnectEnabled=false -DWOStatisticsPassword=stat1st1cs -Der.migration.migrateAtStartup=true -Der.migration.createTablesIfNecessary=true -Dapp.createDummyData=false -DWOAllowsConcurrentRequestHandling=true -DEOAdaptorDebugEnabled=false -Xms512m -Xmx512m
On Jul 13, 2009, at 1:17 PM, George Domurot wrote:
Thanks for the pointers. I'm now95% there.
The frameworks are being embedded, however the web server resources are not being linked up correctly, i.e. they are still pointing towards non-embedded resources, where:
http://www.domain.com/WebObjects/Frameworks/JavaDirectToWeb.framework/WebServerResources/SearchWOBoxMenu.gif
should be:
http://www.domain.com/WebObjects/MyWOApp.woa/Frameworks/JavaDirectToWeb.framework/WebServerResources/SearchWOBoxMenu.gif
I've tried several approaches, adding this to build.properties:
frameworksBaseURL="/WebObjects/${build.app.name}.woa/Frameworks"
--and optionally--
frameworksBaseURL=/WebObjects/${build.app.name}.woa/Frameworks
As well as adding the launch argument under JavaMonitor of:
-WOFrameworksBaseURL /WebObjects/MyWOApp.woa/Frameworks
--and optionally--
-WOFrameworksBaseURL "/WebObjects/MyWOApp.woa/Frameworks"
In all cases, the web server resource URLs remain unchanged.
I'm sure I'm missing something super obvious.
Thanks,
G
On Jul 12, 2009, at 4:33 PM, Kieran Kelleher wrote:
And don't forget this bug (WOL-979) in the new build.xml. Please Vote for it so it gets fixed. Meanwhile make the minor change to the build.xml. Without this change, custom bundle name does not work.
http://issues.objectstyle.org/jira/browse/WOL-979
On Jul 12, 2009, at 7:21 PM, David Holt wrote:
On 12-Jul-09, at 3:25 PM, Pascal Robert wrote:
Le 09-07-12 à 18:04, George Domurot a écrit :
I'm working on a new project and we want to move in the fully embedded direction.
I've reviewed the notes at:
http://wiki.objectstyle.org/confluence/display/WOL/Alternative+Ant+Build+Script+for+Fully+Embedded+and+Split+Install+Bundles
and, everything seems straightforward.
I'm getting the following error:
.../split_embedded_build.xml:105: woapplication doesn't support the "stdFrameworks" attribute
Upon searching the archives, it seems other folks have run into the same issue. The fix noted is to create a new project and replace your build.xml file with the new project's version.
I've tried that, but still come up with the same error.
I'm running the latest WOLips/Eclipse update. I'm sure there is a simple explanation/fix, but I'm coming up short via online searching.
The build.xml in WOLips 3.4.x already include the embedded/split install stuff, no need to use the script from the wiki. Take the build.xml from a new project and put it in the "corrupted" project. The file on the wiki is for 3.3 only.
See here for more explanation:
http://wolips.blogspot.com/2008/09/its-alive.html
David
Thoughts?
Thanks,
George
--
George Domurot
george@xxxxxxxxxxxxxxxxxxxx
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@xxxxxxxxxxxxxxx)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/probert%40macti.ca
This email sent to probert@xxxxxxxx
-------------------------------------------------------
Pascal Robert
Learn WO at WOWODC'09 East in Montréal this August!
http://www.wocommunity.org/wowodc09/east
http://www.macti.ca | http://www.linkedin.com/in/macti
Skype | Twitter | AIM/iChat : MacTICanada
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@xxxxxxxxxxxxxxx)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/programmingosx%40mac.com
This email sent to programmingosx@xxxxxxx
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@xxxxxxxxxxxxxxx)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/kieran_lists%40mac.com
This email sent to kieran_lists@xxxxxxx
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@xxxxxxxxxxxxxxx)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/george%40boxofficetickets.com
This email sent to george@xxxxxxxxxxxxxxxxxxxx
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@xxxxxxxxxxxxxxx)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/kieran_lists%40mac.com
This email sent to kieran_lists@xxxxxxx
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@xxxxxxxxxxxxxxx)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/mschrag%40mdimension.com
This email sent to mschrag@xxxxxxxxxxxxxx
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@xxxxxxxxxxxxxxx)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/george%40boxofficetickets.com
This email sent to george@xxxxxxxxxxxxxxxxxxxx
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list ( Webobjects-deploy@xxxxxxxxxxxxxxx) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/kieran_lists%40mac.comThis email sent to kieran_lists@xxxxxxx
|
