At first, we did use OCM, it wasn't JackRabbit's though, it was JCROM (http://code.google.com/p/jcrom/).
But then, we went, and stayed with, "plain", done-by-hand, DAO objects. We have one DAO for each business object, and those DAOs are maintained by us, not by an automated OCM solution. The reason is that we needed more control sometimes on the (de-)serialization of objects, so we wrote our own DAOs. JCROM did prove to be a very nice solution for "regular" business applications, but ours has special needs. Maybe things changed now, but we didn't look back. Hope this helps. Good luck! On Fri, Apr 27, 2012 at 7:20 AM, Decebal Suiu <[email protected]> wrote: > > Fabián Mandelbaum wrote >> >> In our application we use this last approach, we have a bunch of DAO >> objects, one for each business object, that know how to >> (de-)materialize business objects from/to JCR nodes and properties. >> > > Did you use OCM (annotation, ...) or something like a Jcr Handler (write > your converter for each business objects)? > > Best regards, > Decebal > > > > -- > View this message in context: > http://jackrabbit.510166.n4.nabble.com/JCR-application-design-tp4561691p4592297.html > Sent from the Jackrabbit - Users mailing list archive at Nabble.com. -- Fabián Mandelbaum IS Engineer
