When we started the first OCM prototype in 2005, there were 2 solutions : - Use a "path" attribute in each pojo . or - Use the path as an argument in many ObjectContentManager methods like ocm.insert(String path, Object object)
The first solution has been selected because the path is good candidate for an object id. > I don't know if this has been discussed before, but I think this > requirement somehow ties the beans to jcr which is not nice :) I'm > wondering if there isn't a better way? > you are right. Maybe it is a bad influence from the ORM technologies :-) . I mean, having an id like the path or an UUID is maybe not necessary in our OCM framework. We can review if there is another alternative. br, Christophe
