Changes for page Maven Creating Wonder Applications
Last modified by David Holt on 2022/06/25 01:40
From version 29.1
edited by Greg.Brown
on 2009/02/19 11:01
on 2009/02/19 11:01
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. gbrown1 +XWiki.ldeck - Content
-
... ... @@ -21,12 +21,18 @@ 21 21 22 22 With all the tools ready, it's time to make a Wonder application. 23 23 24 -1. Make a new project File > New > Other project, choose a Maven project: [[image:wolimmave2.gif]] 25 -1. Hit Next 26 -1. Hit Next again 27 -1. Select an archtype, use the local catalog, select the woapplication-archtype, hit Next:!wolimmaven.gif! 28 -1. Fill in appropriate parameters for the woapplication-archtype to set up your new application, hit Finish! 24 +~1. Make a new project File > New > Other project, choose a Maven project: [[image:wolimmave2.gif]] 29 29 26 +2. Hit Next 27 + 28 +3. Hit Next again [[image:wolimmavena.gif]] 29 + 30 +4. Select an archtype, use the local catalog, select the woapplication-archtype, hit Next:!wolimmavenb.gif! 31 + 32 +5. Fill in appropriate parameters for the woapplication-archtype to set up your new application, hit Finish! 33 + 34 +[[image:wolimmaven.gif]] 35 + 30 30 The eclipse plugins now create your application! 31 31 32 32 You should create a WOApplication Run Configuration and add the projects build folder's Java to the classpath as detailed here: [[Maven Running or Debugging as WO Application]], otherwise classes won't be found, etc. ... ... @@ -35,20 +35,38 @@ 35 35 The woapplication-archtype is under construction, so you must fix a few things. 36 36 # Fix the pom.xml. Delete the properties and dependencies sections that the woapplication-archtype created, and paste this into the pom: 37 37 {code:xml} 38 - 44 +... 39 39 <properties> 40 - <woversion>5.3.3</woversion> 46 + <woclassifier>wo54</woclassifier> 47 + <woversion>5.4.3</woversion> 41 41 <wonderversion>5.0.0-SNAPSHOT</wonderversion> 42 42 </properties> 43 43 51 + <!-- the dependency management section defines the characteristics of your dependencies to use when referenced elsewhere --> 52 + <!-- See http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html --> 44 44 <dependencyManagement> 54 + <!-- Only ERExtensions and WOOgnl need a wo53 or wo54 classifier but adding it for all WOnder dependencies safeguards it for any future changes to WOnder --> 45 45 <dependencies> 56 + <!-- in the order you'd like --> 46 46 <dependency> 47 - <groupId>com.webobjects</groupId> 48 - <artifactId>JavaFoundation</artifactId> 49 - <version>${woversion}</version> 58 + <groupId>wonder.core</groupId> 59 + <artifactId>ERExtensions</artifactId> 60 + <version>${wonderversion}</version> 61 + <classifier>${woclassifier}</classifier> 50 50 </dependency> 51 51 <dependency> 64 + <groupId>wonder.core</groupId> 65 + <artifactId>ERPrototypes</artifactId> 66 + <version>${wonderversion}</version> 67 + <classifier>${woclassifier}</classifier> 68 + </dependency> 69 + <dependency> 70 + <groupId>wonder.core</groupId> 71 + <artifactId>WOOgnl</artifactId> 72 + <version>${wonderversion}</version> 73 + <classifier>${woclassifier}</classifier> 74 + </dependency> 75 + <dependency> 52 52 <groupId>com.webobjects</groupId> 53 53 <artifactId>JavaWebObjects</artifactId> 54 54 <version>${woversion}</version> ... ... @@ -58,54 +58,48 @@ 58 58 <artifactId>JavaEOAccess</artifactId> 59 59 <version>${woversion}</version> 60 60 </dependency> 61 - <dependency> 62 - <groupId>wonder.core</groupId> 63 - <artifactId>ERExtensions</artifactId> 64 - <version>${wonderversion}</version> 65 - <classifier>wo53</classifier> 66 - </dependency> 67 67 <dependency> 68 - <groupId>wonder.core</groupId> 69 - <artifactId>ERPrototypes</artifactId> 70 - <version>${wonderversion}</version> 71 - 86 + <groupId>com.webobjects</groupId> 87 + <artifactId>JavaFoundation</artifactId> 88 + <version>${woversion}</version> 72 72 </dependency> 73 73 </dependencies> 74 74 </dependencyManagement> 75 -<!-- Only ERExtensions and WOOgnl need a wo53 or wo54 classifier --> 92 + 93 + <!-- now you just reference the groupId and artifactId of each dependency required. This will work for any child pom also. --> 94 + <!-- See http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html --> 76 76 <dependencies> 77 77 <dependency> 78 78 <groupId>wonder.core</groupId> 79 79 <artifactId>ERExtensions</artifactId> 80 - <version>${wonderversion}</version> 81 - <classifier>wo53</classifier> 99 + <classifier>${wonderclassifier}</classifier> 82 82 </dependency> 83 83 <dependency> 84 84 <groupId>wonder.core</groupId> 103 + <artifactId>WOOgnl</artifactId> 104 + <classifier>${wonderclassifier}</classifier> 105 + </dependency> 106 + <dependency> 107 + <groupId>wonder.core</groupId> 85 85 <artifactId>ERPrototypes</artifactId> 86 - <version>${wonderversion}</version> 87 87 </dependency> 88 88 <dependency> 89 89 <groupId>com.webobjects</groupId> 90 90 <artifactId>JavaFoundation</artifactId> 91 - <version>${woversion}</version> 92 92 </dependency> 93 93 <dependency> 94 94 <groupId>com.webobjects</groupId> 95 95 <artifactId>JavaWebObjects</artifactId> 96 - <version>${woversion}</version> 97 97 </dependency> 98 98 <dependency> 99 99 <groupId>com.webobjects</groupId> 100 100 <artifactId>JavaEOAccess</artifactId> 101 - <version>${woversion}</version> 102 102 </dependency> 103 - 104 104 </dependencies> 105 105 106 106 {code} Fix the versions and classifiers in the pom to be the correct values. 107 107 108 -2. Fix the Application, Session, DirectAction jave files. Theyallshould:{code}import er.extensions.appserver.ERX????{code}But the".appserver."isleftout of the importstatements.126 +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} 109 109 110 110 3. Possibly change web components to extend er.extensions.components.ERXComponent instead of the standard WOComponent. 111 111 4. Possible classpath issues; the eclipse component editor has multiple Component and Display Group tabs.?