|
||||||
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. |
Naked 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 also a download available from the project website on Sourceforge which provides some example applications and other resources. In this screencast I show you how to import and then run one of these example applications in Eclipse, and I go through the other resources available.
6 comments to Naked Objects example ‘claims’ app and other resources |
 |
||||
|
Copyright © 2010 Domain Driven Design using Naked Objects - All Rights Reserved |
||||||
[...] in a series showing how to code with the Naked Objects programming model – we build upon the example claims application and show how to add a property to a domain object, and provide a list of choices (a drop-down list) [...]
[...] http://danhaywood.com/2009/09/17/naked-objects-example-claims-app-and-other-resources/ [...]
[...] http://danhaywood.com/2009/09/17/naked-objects-example-claims-app-and-other-resources/ [...]
[...] allowing us to locate existing domain objects, like Customers or Orders. For example, in the claims example app, we have an EmployeeRepository [...]
[...] now though, let’s see how to use this metamodel API. Recall that in the claims example app we have an EmployeeRepository that defines an allEmployees action. Here’s how we call that [...]
[...] what the Claim (from the example claims app) looks like in [...]