> Personally, I like to approach everything "enterprisey" by using services > > which can be split into different areas of functionality.
That sounds very similar to the highly productive Exposed Domain Model POJOs pattern as described in "POJOs in Action". We've used that pattern very successfully on two major enterprise projects that use transparent persistence (JDO but Hibernate works almost as well). In fact we ended up creating an open source framework (free for commercial and open source use) that helps implement the Exposed Domain Model POJOs pattern in a project called exPOJO available at http://www.expojo.com It does all the necessary dependency injection and also provides JDO and Hibernate wrappers so your POJOs can stay 'persistence engine agnostic'. It's very small, lightweight and easy to use - a bit like Spring was before it tried to do everything. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
