Skip to Content
Last modified by Klaus Berkling on 2011/09/06 00:31
From version 21.1
edited by arroz
on 2007/12/20 11:10
Change comment: There is no comment for this version
To version 20.1
edited by Pascal Robert
on 2011/09/06 00:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.arroz
1 +XWiki.probert
Content
... ... @@ -1,6 +1,6 @@
1 1  {{warning title="In construction"}}
2 2  
3 -This chapter is under construction. Do not expect it to be useful... yet! :)
3 +This chapter is under construction. Do not expect it to be useful... yet\! :-)
4 4  
5 5  {{/warning}}
6 6  
... ... @@ -50,7 +50,7 @@
50 50  
51 51  That's it. This will create a new WO application, ready to be used with WONDER.
52 52  
53 -If you want to integrate WONDER with and existing Application, you must follow **all** the steps described in the [[integration page of the WONDER wiki>>WONDER:Integrate Wonder Into an Existing Application]]. Note that it's not just adding the frameworks to the project, you really have to make all the code changes described there (it's easy to do, but don't skip it, or you'll have problems).
53 +If you want to integrate WONDER with and existing Application, you must follow **all** the steps described in the [[integration page of the WONDER wiki>>Integrate Wonder Into an Existing Application]]. Note that it's not just adding the frameworks to the project, you really have to make all the code changes described there (it's easy to do, but don't skip it, or you'll have problems).
54 54  
55 55  == Keep all the model functionality on a framework ==
56 56  
... ... @@ -72,12 +72,10 @@
72 72  
73 73  1. Right-click on your application project icon, and choose "Properties" from the contextual menu.
74 74  1. Choose "Java Build Path" from the list on the left.
75 -1. Click on the "Projects" tab on the right.
76 -1. Click the "Add..." button and choose your framework. Click "OK" to close the projects window.
77 -1. Click "OK" to close the project properties window.
75 +1. Click on the "Libraries" tab on the right.
76 +1. Click the "Add Library" button, select "WebObjects Frameworks", click "Next" and choose your framework. Click "OK" to close the Build Path window.
77 +1. Done. Now you're project is linking with your framework. If you think this is overkill, think again when you need to do a maintenance application of a backoffice. You'll love the time you spent separating the model code from the application. Also, this helps you write better code, because model code shouldn't need to know anything about the presentation layer. If you try to do that in your framework, you'll get an error, so you really can't do it :-)
78 78  
79 -Done. Now you're project is linking with your framework. If you think this is overkill, think again when you need to do a maintenance application of a backoffice. You'll love the time you spent separating the model code from the application. Also, this helps you write better code, because model code shouldn't need to know anything about the presentation layer. If you try to do that in your framework, you'll get an error, so you really can't do it! :)
80 -
81 81  If you don't want to create the model framework now, at least take the advice of keeping the model layer fully independent from the presentation layer. This will make it easier if you decide, in the future, to separate the model code to a framework as described here.
82 82  
83 -[[« Overview>>Best Practices]] [[Model »>>Best Practices-Model]]
81 +[[« Overview>>WO:Best Practices]] [[Model »>>Best Practices-Model]]