> Chris Colman wrote: > > It seems it's also possible for a few other ORM tools to conform to that > standard. Apart from Hibernate and JPOX you've got TopLink, Cayenne and > others.
That's my point. > > Which would you rather depend on; exPOJO or JPA? Two different things: exPOJO is a lightweight, dependency injection framework with support for the "exposed POJO domain model pattern" for highly productive app development. It provides a very concise and simple interface declaring the essential generic services of a transparent persistence engine. 'Transparent' is the key word here so the interface needs only be extremely minimal but this generic interface is massively powerful. Out of the box it has JDO and Hibernate implementations of this interface and others (including JPA) can be supported in under 60 minutes if required. JPA is a different thing altogether - it's an ORM standard. The trouble is that it had to make compromises to allow certain popular ORMs to implement it. exPOJO does not try to be another ORM standard. It just takes the best the exposed domain model pattern has to offer and uses that such that the only components with engine specific references are the repository components that you build that have engine specific queries in them. All the rest can be handled generically. > > /Anders > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
