Skip to Content
Last modified by Klaus Berkling on 2012/06/20 12:13
From version 16.1
edited by Kieran Kelleher
on 2007/10/01 22:08
Change comment: There is no comment for this version
To version 21.1
edited by Klaus Berkling
on 2012/03/01 19:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.kieran
1 +XWiki.kberkling@dyned_com
Content
... ... @@ -5,11 +5,13 @@
5 5  
6 6  == Minimum Wonder Integration ==
7 7  
8 -* Add ERJars, ERExtensions and Wonder's JavaWOExtensions frameworks to your project's framework references
8 +* Add ERJars, ERExtensions, WOOgnl and Wonder's JavaWOExtensions frameworks to your project's framework references
9 +* Add ERPrototypes if your EO model uses/will use prototypes
9 9  * Remove existing log4j jar if your project had that.
10 10  * Make it so your Application class subclasses ERXApplication
11 11  * Make it so your Session class subclasses ERXSession
12 12  * Make it so your DirectAction classes extend ERXDirectAction
14 +* Make it so your Enterprise Objects extend ERXGenericRecord instead of EOGenericRecord. If you use EOGenerator, simply change your superclass template class declaration and import statements.
13 13  * Your Application class' main static method **{+}must{+}** call ERXApplication.main(...) instead of WOApplication.main(...). Your application will fail to initialize and launch otherwise.
14 14  * Use ERXEC.newEditingContext() to create new editing contexts in your application
15 15  * Add minimal content to Properties file. To get minimal content, create a temporary empty project using the WOnderApplication WOLips project template and copy/paste the contents from that template's Properties file.
... ... @@ -31,7 +31,8 @@
31 31  
32 32  If you got the minimum Wonder integration done and your app is working, then adding these extra fundamental useful frameworks are definitely worthwhile from the start:
33 33  
34 -* ERPrototypes - save yourself lots of manhours fiddling with EOModel attributes by using convenient prototypes. This is considered best practice.
36 +* Ajax - Just what it says - easy Ajax in your WO apps
37 +* ERPrototypes - save yourself lots of manhours fiddling with EOModel attributes by using convenient prototypes. This is considered best practice. (Don't forget to select a prototype in your database database config in Entity Modeler, otherwise the prototype won't show up when adding/editing an attribute.)
35 35  * ERJavaMail - send all kinds of emails - plain text, html, multi-part, attachments, etc. HTML can be generated from a WOComponent or be set using a HTML String.
36 36  * ERSelenium - functional testing that simulates user interaction with your app's web pages.
37 37  
... ... @@ -41,9 +41,7 @@
41 41  {{/tip}}
42 42  
43 43  {{info value="Start Your Next Project on the Right Foot"}}
44 -
45 45  For your next project, simply select the WOnderApplication project template instead of the WOApplication template and all the minimum integration tasks itemized above are already done for you. Besides, the WOnder Application project template is so neatly organized that some have commented on how it is a better overall project template for WebObjects projects even if you are not using Wonder.
48 +\\ !Picture 9.jpg!
46 46  
47 -
48 -
49 49  {{/info}}