Hi Tor, Good Point. We worked with a fine grained Diff until it became too big.
I would probably like to mention the following additions as my top ten list ;) --- (1) Query extionsions mainly around extended support for SQL specifically JOINs We also introduced Java Bindings for the Query Object model that allow for easier "query wizards" and last but not least "Prepared" queries (2) Access Control Management to go beyond the introspection that is already specified in JCR v1.0 (3) Retention & HoldSupport to enable records management applications sitting on top of JCR repositories in a standardized fashion (4) Simple versioning to provide for repositories that only support linear versioning. Versioing extensions around "Baselines" and "Activities" to cover the full configuration management spectrum (5) Lifecycle Management to allow to easily hook content into a process engine. (6) Standardized Nodetype Registration that allow application to register and manage their nodetypes with repository. (7) New property types and new Nodetypes to enhance application interoperability around common meta data (8) Workspace Management to allow for creation and deletion of workspaces in a repository (9) Shareable nodes that allow the tree in a content repository workspace to become a more implicit network. (10) Journalling Observation that allows offline/polling applications to find out what happend in a content repository since they last checked. --- .... is that helpful? regards, david On 7/16/07, Torgeir Veimo <[EMAIL PROTECTED]> wrote:
On Mon, 2007-07-16 at 10:06 +0200, David Nuescheler wrote: > Dear Jackrabbit Community, > > I am happy to report on behalf of the JSR-283 Expert Group that JCR v2.0 > has reached public review status. > > During the next 60 days we will collect input from the general public about > the changes that the Expert Group propose to JCR. There's no 'what's changed' section? The whole document is 450+ pages long so this would be handy. -- -Tor
