Hi Tom, I believe that you are using JCR exactly right. There are many reasons why JCR is better suited for object persistence than an RDBMS, understanding inheritance to just mention one. You may find an ongoing effort to offer Object-Content-Mapping in Graffito http://incubator.apache.org/graffito/jcr-mapping/index.html
I am convinced that the reason that we see so many "Content Applications" that revolve around Document Management, Wiki's or other classical CMS applications is really lack of imagination ;) . You may find my views on that particular subject in the following presentation that I recently gave at the Content Managent Forum in Denmark: http://www.day.com/o.file/cmf-2006.pdf?get=073d75dc38e1f3af470652f5e9086972 (Slides 31-35 are speaking about that very topic) regards, david On 2/2/07, Tom Wheeler <[EMAIL PROTECTED]> wrote:
I currently have a subsystem in a project I'm working on that provides object persistence, caching, reference resolution and change notification. I also need to support additional capabilities in the future such as transactions and versioning. I came across Jackrabbit somewhat by accident last week and am new to JCR in general. However, it seems like Jackrabbit does much of what I need already, and I could easily wrap it to provide the rest. In fact, I've got a simple proof-of-concept working already. Much of what I've read so far seem focused on content and document management applications like blogs, wikis and CMS systems. Is what I'm trying to do a misuse of JCRs? Is there some open source framework on top of Jackrabbit already that makes it easier to use them for general persistence of complex Java objects? -- Tom Wheeler http://www.tomwheeler.com/
