|
||||||
Domain-driven design (DDD) focuses on what matters in enterprise applications: the core business domain. And Naked Objects lets you build DDD applications just by writing the core domain classes, the rest of the application is taken care of for you. This blog supplements and expands on my book, Domain Driven Design using Naked Objects, describing how you can rapidly develop and test domain applications using Naked Objects. |
Using the Naked Objects 4.0 Maven Archetype
The first in a series of screencasts on using Naked Objects and its sister projects. This one shows how to get started using the Maven archetype that comes with Naked Objects 4.0. For a larger view, click play and then press the button in the bottom right.
5 comments to Using the Naked Objects 4.0 Maven Archetype |
 |
||||
|
Copyright © 2010 Domain Driven Design using Naked Objects - All Rights Reserved |
||||||
typo: Mavn != Maven
Ta.
Great book. Be warned, if you or your company use a content filter on your network you can get some pretty strange errors when trying to create projects. Mine kept blocking “nakedobjects” resulting in many hours spent tracking down mysterious errors when trying to process the pom.xml files…… once I added maven.org to the exception site list all worked well..
[...] http://danhaywood.com/2009/08/29/using-the-naked-objects-4-0-maven-archetype/ [...]
[...] Objects example ‘claims’ app and other resources As I blogged about in previously, Naked Objects is available from the Maven central repository. But to get you started there’s [...]