JCR 2.0 Support

[boomah]

Hi all.

I've just started with this and I added the dependency to my pom file with the latest version (1.0.0.Beta1).

When inspecting the jars it downloaded, I noticed that jcr-1.0.1.jar is used.

Any idea when ModeShape will depend on 2.0?

Thanks, Paul.

[rhauch]

Thanks for giving ModeShape a try!

Yes, ModeShape does implement the JCR 1.0 API. When we started the project a few years ago, JSR-283 was still very much up in the air. In fact, JSR-283 was only recently finalized.

Since most existing JCR applications are still using JCR 1.0, we thought it best to first release ModeShape with support for the 1.0 API. We do plan to start the work on the 2.0 API features pretty soon (actually, a number of our existing features were designed with the 2.0 API in mind), but haven't yet formalized it on the roadmap. Also, ModeShape 1.0.0.Beta1 already supports the JCR-SQL2 query language.

What features of the 2.0 API are you interested in using?

[boomah]

Thanks for the response.

There are no features of the 2.0 api in particular that I was after.

I've been asked to investigate a document storage solution for a new project which, at first, has rather basic requirements. I need to associate files (pdf's, images) with a certain entity with store/retrieve, versioning and perhaps text search (in the pdf's, not images obviously).

I noticed when trying jackrabbit that some of the versioning api calls have been deprecated in 2.0 and I just didn't want to get caught out before I had started.

Thanks, Paul.

[rhauch]

There are no features of the 2.0 api in particular that I was after.

I've been asked to investigate a document storage solution for a new project which, at first, has rather basic requirements. I need to associate files (pdf's, images) with a certain entity with store/retrieve, versioning and perhaps text search (in the pdf's, not images obviously).

Let us know what you find and which 2.0 features (if any) you end up liking/needing so we can prioritize. Thanks!

I noticed when trying jackrabbit that some of the versioning api calls have been deprecated in 2.0 and I just didn't want to get caught out before I had started.

We'll support all of the JCR 1.0 API versioning methods when that feature is finished in 1.1.

[rhauch]

I just started a new thread to discuss a re-prioritization of JCR 2.0: http://community.jboss.org/message/544269