New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Investigate support for JCR #35

Closed

GoogleCodeExporter opened this issue Apr 4, 2015 · 1 comment

Labels

auto-migrated Priority-Medium Type-Enhancement

GoogleCodeExporter commented Apr 4, 2015

Don't know if it is possible to support JCR **easily**, but reading through the 
spec should give some (new) ideas at least.

Original issue reported on code.google.com by maik.jablonski@gmail.com on 7 Dec 2010 at 8:35

The text was updated successfully, but these errors were encountered:

Author

GoogleCodeExporter commented Apr 4, 2015

It should be straightforward to create a migration script from Jease to JCR. So 
if someones want to use a CMS based on JCR, he can migrate the content. Jease 
is built on the notion of "object databases in prevayler mode", so too much 
flexibility would be lost implementing JCR.

Original comment by maik.jablonski@gmail.com on 10 Mar 2011 at 12:35

Changed state: WontFix

GoogleCodeExporter added Priority-Medium auto-migrated Type-Enhancement labels

GoogleCodeExporter closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment