Wicket Objects consists of a main viewer, along with some optional views. There is also a simple test application:
- The main viewer (trunk/main) depends only on Wicket, formally released into the Maven central repo.
- The optional views (trunk/views/view-xxx are more experimental, depending on different contributions from "wicketstuff". wicketstuff is also available in the Maven central repo.
- The test application (trunk/testapp) is a version of the standard claims app.
Wicket Objects does not run against NOF 4.0.0; instead you'll need to build NOF from source, ie needs to be built against NOF 4.0.1-SNAPSHOT or later.
To build NOF from source, use: svn co https://nakedobjects.svn.sourceforge.net/svnroot/nakedobjects/trunk nakedobjects-trunk
- cd pom
- mvn clean install
- cd ..
- mvn clean install
Check out Wicket Objects from trunk:
svn co https://wicketobjects.svn.sourceforge.net/svnroot/wicketobjects wicketobjects
If you want a particular revision, eg rev 165, then use:
svn co -r165 https://wicketobjects.svn.sourceforge.net/svnroot/wicketobjects wicketobjects
Main Viewer & Test app
I use m2eclipse to import projects; this recursively includes all submodules. Import:
- wicketobjects' trunk/main
- wicketobjects' trunk/testapp
To run the app:
- first make sure it isn't referencing any of the view-xxx modules
- use the launch configuration in testapp/claims/commandline/eclipse-launch
- this runs org.nakedobjects.webserver.WebServer?, picking up the contents of web.xml
- login using sven/pass.
Trying out the views
You can try out different views by editing classpath (ie the pom.xml of the testapp's commandline project.
This view uses gmap2 (part of wicketstuff) to provide a google maps mashup:
- Import wicketobject's trunk/views/view-gmap2
- edit the testapp's commandline pom.xml to reference view-gmap2.
- run the testapp; any collection of Locatable objects (ie Employee) should be rendered in a google map.
This view uses googlecharts (part of wicketstuff) to provide a google charting:
- Import wicketobject's trunk/views/view-googlecharts
- edit the testapp's commandline pom.xml to reference view-googlecharts.
- run the testapp; any collection of PieChartable objects (ie ClaimExpenseSummary should be rendered in a pie chart
This doesn't depend on wicketstuff; it's an alternative application menu bar.
- edit the testapp's commandline pom.xml to reference view-cooldatasoftmenu.
- run the testapp; the application menu bar should be rendered differently
This uses wicketstuff's calendarviews. It is considered experimental, so may not work exactly as expected.
- Import wicketobject's trunk/views/view-calendarviews
- edit the testapp's commandline pom.xml to reference view-calendarviews.
- run the testapp; any collection of Calendarable objects (ie Claim) should be rendered in a calendar view.
NB: the calendarviews doesn't seem to be particularly finished, so this is the most experimental of the views
This website is hosted by Trac (see [TracNotes] for more info).