The todo app (quickstart) archetype will generate a reasonably complete application for tracking to-do items, based around a single domain class
ToDoItem and repository,
While not quite a "kitchen-sink" example (there is, after all, just a single domain class), the app nevertheless demonstrates a good number of Isis' capabilities. In particular, the use of contributed actions etc is demonstrated by
ToDoItemContributions; view models are demonstrated by
ToDoItemsByDateRangeViewModel; a dashboard is demonstrated by
The archetype also demonstrates Isis' support for in-built profiling, auditing, event publishing and background actions. The last of these integrates with the Quartz scheduler, executing queued-up actions every 10 seconds.
Running this archetype is a good way to get familiar with the structure of a not-too-complex Isis application. However, to get started with your own application, we generally recommend that you run the alternative simple archetype. This will generate a completely stripped back and minimal application for you to refactor and extend; you can then use this ToDo app to guide your own development.
How to use the Apache Isis quickstart archetype to generate your first Apache Isis application.
A run-through of the main features of the todo application generated by the Apache Isis quickstart archetype (as of v1.4.0).
An earlier screencast, relating to v1.2.0, is available here.>
Create a new directory, and
cd into that directory.
Then run the following command:
mvn archetype:generate \ -D archetypeGroupId=org.apache.isis.archetype \ -D archetypeArtifactId=quickstart_wicket_restful_jdo-archetype \ -D archetypeVersion=1.5.0 \ -D groupId=com.mycompany \ -D artifactId=myapp \ -D version=1.0-SNAPSHOT \ -B
groupIdrepresents your own organization, and
artifactIdis a unique identifier for this app within your organization.
versionis the initial (snapshot) version of your app.
The archetype generation process will then run; it only takes a few seconds.
Switch into the root directory of your newly generated app, and build your app:
cd myapp mvn clean install
myapp is the
artifactId entered above.
quickstart_wicket_restful_jdo archetype generates a single WAR file, configured to run both the Wicket viewer and the Restful Objects viewer. The archetype also configures the JDO Objectstore to use an in-memory HSQLDB connection.
Once you've built the app, you can run the WAR in a variety of ways.
The recommended approach when getting started is to run the self-hosting version of the WAR, allowing Isis to run as a standalone app; for example:
java -jar viewer-webapp/target/myapp-viewer-webapp-1.0-SNAPSHOT-jetty-console.war
This can also be accomplished using an embedded Ant target provided in the build script:
mvn -P self-host antrun:run
prior to v1.5.0, this was simply: mvn antrun:run
The first is to simply deploying the generated WAR (
webapp/target/myapp-webapp-1.0-SNAPSHOT.war) to a servlet container.
Alternatively, you could run the WAR in a Maven-hosted Jetty instance, though you need to
cd into the
cd webapp mvn jetty:run -D jetty.port=9090
In the above, we've passed in a property to indicate a different port from the default port (8080).
Note that if you use
mvn jetty:run, then the context path changes; check the console output (eg http://localhost:9090/myapp-webapp).
Finally, you can also run the app by deploying to a standalone servlet container such as Tomcat.
The archetype provides a welcome page that explains the classes and files generated, and provides detailed guidance and what to do next.
The app itself is configured to run using shiro security, as configured in the
WEB-INF/shiro.ini config file. To log in, use
Once you are familiar with the generated app, you'll want to start modifying it. There is plenty of guidance on this site; check out the 'programming model how-tos' section on the main documentation page first).
If you use Eclipse, do also install the Eclipse templates; these will help you follow the Isis naming conventions.
As noted above, the generated app is a reasonably complete application for tracking to-do items. It consists of the following modules:
|myapp||The parent (aggregator) module|
|myapp-dom||The domain object model, consisting of ToDoItem and ToDoItems (repository) domain service.|
|myapp-fixture||Domain object fixtures used for initializing the system when being demo'ed or for unit testing.|
|myapp-integtests||End-to-end integration tests, that exercise from the UI through to the database|
|myapp-webapp||Run as a webapp (from web.xml) using either the Wicket viewer or the RestfulObjects viewer|
If you run into issues, please don't hesitate to ask for help on the users mailing list.
All edits are reviewed before going live, so feel free to do much more than fix typos or links. If you see a page that could benefit from an entire rewrite, we'd be thrilled to review it. Don't be surprised if we like it so much we ask you for help with other pages :)NOTICE: unless indicated otherwise on the pages in question, all editable content available from apache.org is presumed to be licensed under the Apache License (AL) version 2.0 and hence all submissions to apache.org treated as formal Contributions under the license terms.