Alex, Thanks for your comments. You are welcome to create new Jira issues & send us patches. Your help will be very appreciated.
Here is my comments : On Jan 28, 2008 1:05 PM, Alex Lukin <[EMAIL PROTECTED]> wrote: > Monday 28 January 2008 13:07:25 Christophe Lombart написав: > > > > There is also the annotation support in Jackrabbit OCM. > > ... but ok the doc is missing :-) > > > Well, what if good OCM in my humble opinion? Yes, documented with > examples! :) > > 0. It must work recursive because we work with tree. OCM is recursive. > > > 1. It does not demand a lot of efforts or takes no time for writing > mappings. > No long XMLs. Annotations just OK, my be even annotations that available > at > run-time. Developer just registers classes with required annotations and > system knows how to work with them. > It is working like this now. > > 2. OCM must check class and class versions while loading of saving nodes. > What > to do if something goes wrong? I decided to take "best effort" strategy. > We > map what we can and leave data untouched if in doubt. and yes, we strictly > warn developer and admin. > Can you give more details ? > > 3. OCM must have possibility to find typed objects by parameters and by > types. > I don't understand please can you give more details ? > > 4. OCM must have transactional manager just like in JPA or EJB 3.0 > It is possible to use the Tx Jackrabbit stuff. We are reviewing the Spring module integration in order to have a more flexible tx support. Other solutions are welcome. > > 5. JCR path shoud never be mapping parameter. This is runtime parameter > because one can retrive same data types from different places. see the discussion here : http://www.mail-archive.com/[EMAIL PROTECTED]/msg09960.html > > > > > A couple of words about recursion. There are 2 different apects. First, > you > may have class that contains link to itself. It is very convinient for > things > like categories and so on. But this is infinite recursion and I use "deep" > property to make it finite. What is a deep property. We have the same problem but is it managed differently (with a small cahe) > Second, when class has properties as class > instance that has properties as class instance etc... We must go down to > simple types and make nodes for all of it. May be good solution id > annotation > inheritance for this case. If some property marked as persistent so all > stuff > that containde in property myst be marked as persistent. I'm not sure if I understand correctly but in OCM we are managing this with BeanDescriptors & CollectionDescriptors.
