Last modified by David Holt on 2022/06/25 01:40

From version 31.1
edited by Greg.Brown
on 2009/02/19 11:00
Change comment: There is no comment for this version
To version 25.1
edited by Lachlan Deck
on 2009/02/20 11:22
Change comment: Fixing pom definition

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.gbrown
1 +XWiki.ldeck
Content
... ... @@ -21,11 +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. Select an archtype, use the local catalog, select the woapplication-archtype, hit Next:
27 -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]]
28 28  
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 +
29 29  The eclipse plugins now create your application!
30 30  
31 31  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.
... ... @@ -36,18 +36,36 @@
36 36  {code:xml}
37 37  
38 38   <properties>
39 - <woversion>5.3.3</woversion>
46 + <woclassifier>wo54</woclassifier>
47 + <woversion>5.4.3</woversion>
40 40   <wonderversion>5.0.0-SNAPSHOT</wonderversion>
41 41   </properties>
42 42  
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 -->
43 43   <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 -->
44 44   <dependencies>
56 + <!-- in the order you'd like -->
45 45   <dependency>
46 - <groupId>com.webobjects</groupId>
47 - <artifactId>JavaFoundation</artifactId>
48 - <version>${woversion}</version>
58 + <groupId>wonder.core</groupId>
59 + <artifactId>ERExtensions</artifactId>
60 + <version>${wonderversion}</version>
61 + <classifier>${woclassifier}</classifier>
49 49   </dependency>
50 50   <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>
51 51   <groupId>com.webobjects</groupId>
52 52   <artifactId>JavaWebObjects</artifactId>
53 53   <version>${woversion}</version>
... ... @@ -57,54 +57,48 @@
57 57   <artifactId>JavaEOAccess</artifactId>
58 58   <version>${woversion}</version>
59 59   </dependency>
60 - <dependency>
61 - <groupId>wonder.core</groupId>
62 - <artifactId>ERExtensions</artifactId>
63 - <version>${wonderversion}</version>
64 - <classifier>wo53</classifier>
65 - </dependency>
66 66   <dependency>
67 - <groupId>wonder.core</groupId>
68 - <artifactId>ERPrototypes</artifactId>
69 - <version>${wonderversion}</version>
70 -
86 + <groupId>com.webobjects</groupId>
87 + <artifactId>JavaFoundation</artifactId>
88 + <version>${woversion}</version>
71 71   </dependency>
72 72   </dependencies>
73 73   </dependencyManagement>
74 -<!-- 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 -->
75 75   <dependencies>
76 76   <dependency>
77 77   <groupId>wonder.core</groupId>
78 78   <artifactId>ERExtensions</artifactId>
79 - <version>${wonderversion}</version>
80 - <classifier>wo53</classifier>
99 + <classifier>${wonderclassifier}</classifier>
81 81   </dependency>
82 82   <dependency>
83 83   <groupId>wonder.core</groupId>
103 + <artifactId>WOOgnl</artifactId>
104 + <classifier>${wonderclassifier}</classifier>
105 + </dependency>
106 + <dependency>
107 + <groupId>wonder.core</groupId>
84 84   <artifactId>ERPrototypes</artifactId>
85 - <version>${wonderversion}</version>
86 86   </dependency>
87 87   <dependency>
88 88   <groupId>com.webobjects</groupId>
89 89   <artifactId>JavaFoundation</artifactId>
90 - <version>${woversion}</version>
91 91   </dependency>
92 92   <dependency>
93 93   <groupId>com.webobjects</groupId>
94 94   <artifactId>JavaWebObjects</artifactId>
95 - <version>${woversion}</version>
96 96   </dependency>
97 97   <dependency>
98 98   <groupId>com.webobjects</groupId>
99 99   <artifactId>JavaEOAccess</artifactId>
100 - <version>${woversion}</version>
101 101   </dependency>
102 -
103 103   </dependencies>
104 104  
105 105  {code} Fix the versions and classifiers in the pom to be the correct values.
106 106  
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.
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}
108 108  
109 109  3. Possibly change web components to extend er.extensions.components.ERXComponent instead of the standard WOComponent.
110 110  4. Possible classpath issues; the eclipse component editor has multiple Component and Display Group tabs.?