I'm just going to focus on the bits that are close to my heart (I don't have any issues with the rest, though)... continued below...
On 23 Nov 2011 at 17:26, Dan Haywood wrote: > ~~~ > Alexander's slightly tongue-in-cheek question is funny, cos actually > long-term I do think that Isis should lose its persistence layer. My view > is that the fact that it can only be deployed on the handful of > objectstores that we have implementations for counts against it. In time I > would like to simplify the whole, rather complex, runtime/back-end, and > plug into JDO or JPA or maybe have a really lightweight implementations > around NoSQL (eg Mongo). I just read a little about Cayenne[1]. Has anyone used it? I am particularly anti any DAL that *requires* additional annotations or XML files or other extra bits to support persistence. I resent Hibernate, OpenXava, etc. As it stands, the Isis SQL/JDBC objectstore works (but is perhaps not suited for large scale production use - let me know if you've tried and failed). And it works automatically, as far as the domain developer is concerned. It even supports polymorphic domain objects. (Yes, yes, it could do with some improvements.. I have some ideas, already). I am happy for the Isis Persistence API / Objectstore API to be simplified (can't actually say I really noticed the split, myself), and I do see advantages to making some Objectstore functionality more apparent (accessible) to the domain (e.g. pagination, custom queries). But, having said that, I would like to see how is it possible to integrate with other store technologies (JDO/Cayenne/etc) - but, to me, it must be seamless - only requiring "something extra" when you're trying to do something special (What special? To be determined). Regards, Kevin [1] http://cayenne.apache.org/
