Skip to Content
Last modified by David Holt on 2022/06/25 01:40
From version 35.1
edited by Greg.Brown
on 2009/02/19 10:53
Change comment: There is no comment for this version
To version 34.1
edited by Greg.Brown
on 2009/02/18 15:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -13,7 +13,7 @@
13 13  
14 14  One reasonable way to get and maintain the Wonder sources is have a directory which holds all the sources (see here: [[Download Wonder Source>>http://wiki.objectstyle.org/confluence/display/WONDER/Download+Wonder+Source%2C+Build+and+Install]]), then use Maven to install and build Wonder (see here: [[Building the wonder source code with maven]]).
15 15  
16 -Several things you should know, currently:
16 +Several things you should know:
17 17  
18 18  * Wonder is built using a maven "build profile", e.g. "mvn clean install --P wo53" builds things for a WebObjects 5.3.x environment and "mvn clean install --P wo54" builds things for a WebObjects 5.4.x environment.
19 19  * The only frameworks which are different because of this are ERExtensions and WOOgnl.
... ... @@ -107,7 +107,5 @@
107 107  2. Fix the Application, Session, DirectAction jave files. They all should: {code}import er.extensions.appserver.ERX????{code} But the ".appserver." is left out of the import statements.
108 108  
109 109  3. Possibly change web components to extend er.extensions.components.ERXComponent instead of the standard WOComponent.
110 -4. Possible classpath issues; the eclipse component editor has multiple Component and Display Group tabs.?
111 -5. Main component is NSMacOSRomanStringEncoding, non-Maven Wonder apps use "UTF-8" in the woo.
112 112  
113 113  {{/note}}