Jackrabbit 3
In February 2010 we started a series of design discussions for Jackrabbit 3.
A generic search on markmail for all jr3 threads
The main threads are:
- Jackrabbit 3: repository requirements
- Jackrabbit 3: architectural changes
- [http://markmail.org/message/vv7mohr22uqdugah]
- [http://markmail.org/message/mbhiocfpix5w7y5u]
- [http://markmail.org/message/bijbl5s5wfvmouhx]
- [http://markmail.org/message/kay2gctv2pg52o4y]
- [http://markmail.org/message/dclsybirtojxlxla]
- [http://markmail.org/message/v2wl5nh43zf2shkp]
- [http://markmail.org/message/odsn724erduthh7u]
- [http://markmail.org/message/y4djywx36r6bc2me]
- [http://markmail.org/message/vear2yjdtdqhpog5]
- [http://markmail.org/message/4ergosyctvd47t7x]
- [http://markmail.org/message/g6mnjsnn6txcebvf]
- [http://markmail.org/message/4z2kw7qgkmqbwpsm]
- [http://markmail.org/message/i65h4uennrbv6ttb]
- [http://jackrabbit.markmail.org/thread/3jzqjy6cavxcrpbq]
- ...
Prototypes
Other ideas
- Transactional versioning
- Node type management
- Hot backup
- Full XPath
- NGP (or something similar)
- Point in time recovery
- Native clustering
- JDBC over JCR
Completed in Jackrabbit 2.0
- JCR 2.0
- WebDAV remoting
- Database connection pooling
- Built-in access control