> At first I wanted to have each entity be two classes: XBean, containing > the business logic and abstract get/sets, and then XJDBC which > subclasses XBean and implements ejbLoad/ejbStore for BMP. But that > didn't quite work, so instead I made a superclass EntitySupport that > XBean could extend, and in EntitySupport.ejbLoad/ejbStore I delegate to > a DAO object that handles the JDBC. This is really cool because it means > that I can very easily switch persistence mechanism by simply making a > factory mechanism for the DAO handlers :-) So, for example, during dev > I'd use a simple XML storage, or db4o, and then for production I'd > switch to JDBC, but without having to change my code at all. >
Rickard, Care to share any further insights about your approach? Are you using xdoclet for the DAOs as well ? What about the factory mechanism ? Hand coded ? Any other patterns in use there Thanks for any more info you can provide Matthew _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
