Skip to Content
Last modified by David Holt on 2022/06/25 01:40
From version 22.1
edited by Lachlan Deck
on 2009/02/20 11:26
Change comment: pom fix
To version 17.1
edited by Greg.Brown
on 2009/02/28 16:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ldeck
1 +XWiki.gbrown
Content
... ... @@ -1,7 +1,7 @@
1 1  = Creating Wonder Applications using Maven + m2eclicpse =
2 2  
3 3  {{note}}
4 - Under Construction
4 + Under Construction - but still a good starting point
5 5  {{/note}}
6 6  
7 7  If you want to use Wonder in your applications (and why woundn't one) you must be correctly setup with:
... ... @@ -125,7 +125,7 @@
125 125  2. Fix the Application, Session, DirectAction jave files import statements. As of this writing the import statements are incorrect for Wonder 5.0 which refactored all its classes into packages other than {code}er.extensions{code}. So just right click on These three files and choose Source > Organize Imports which should, as of this writing, make them {code}import er.extensions.appserver.ERX...{code}
126 126  
127 127  3. Possibly change web components to extend er.extensions.components.ERXComponent instead of the standard WOComponent.
128 -4. Possible classpath issues; the eclipse component editor has multiple Component and Display Group tabs.?
128 +4. The "Properties" file is blank, you can copy one from a non Maven Wonder Application.
129 129  5. Main component is NSMacOSRomanStringEncoding, non-Maven Wonder apps use "UTF-8" in the woo.
130 130  
131 131  {{/note}}