Re: Jackrabbit 3: extracting same name sibling support from the core

Hi, > Is this could be an optional feature in 3.X? As JCR 2.X is out and it could > raise comparability problem, right? This change wouldn't affect the public API. SNS would still be supported as they are done now. Maybe with a few changes, but all within the JCR 2.0 specification. About compat

Re: Jackrabbit 3: extracting same name sibling support from the core

On Thu, Feb 11, 2010 at 12:54 PM, Thomas Müller wrote: > Hi, > > About SNS (same name siblings): what about moving that part away from > the "core"? Currently, the Jackrabbit architecture is (simplified): > > 1) API layer (JCR API, SPI API) > 2) Jackrabbit core, which knows about SNS > > After mov

Re: Jackrabbit 3: extracting same name sibling support from the core

On Thu, Feb 11, 2010 at 11:54 AM, Thomas Müller wrote: > About SNS (same name siblings): what about moving that part away from > the "core"? Currently, the Jackrabbit architecture is (simplified): > > 1) API layer (JCR API, SPI API) > 2) Jackrabbit core, which knows about SNS > > After moving the

Re: Jackrabbit 3: extracting same name sibling support from the core

On Thu, Feb 11, 2010 at 12:54, Thomas Müller wrote: > After moving the SNS support, it would be something like this: > > 1) API layer (JCR API, SPI API) > 2) SNS support code, which knows about SNS, and maps SNS node names > to/from internal node names > 3) Jackrabbit core, doesn't know anything a

Jackrabbit 3: extracting same name sibling support from the core

Hi, About SNS (same name siblings): what about moving that part away from the "core"? Currently, the Jackrabbit architecture is (simplified): 1) API layer (JCR API, SPI API) 2) Jackrabbit core, which knows about SNS After moving the SNS support, it would be something like this: 1) API layer (JC

Re: Upgrade from 1.5.5 to 2.0.0 was unsuccessful in clustered environment: Cause: java.sql.SQLException: Lock wait timeout exceeded; Any ideas?

Hi, > Could you point me in the right direction for a production-ready model 3 > deployment model (where we can access the repository remotely)? There is some documentation available here: http://wiki.apache.org/jackrabbit/RemoteAccess Regards, Thomas

[jira] Updated: (JCR-936) Using Oracle bundle PM throws SQL exception (cannot insert NULL)

[ https://issues.apache.org/jira/browse/JCR-936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martijn Hendriks updated JCR-936: - Attachment: JCR-936.patch Here's another patch that improves the logging of schema creation. Note th

Why becomes my Repository bigger and bigger?!

Hello all together, i have a problem with the size of my repository. First I registered 22 Node-Types. There is one Node-Type, which is the "Main-Node-Type" and 21 other Node-Types, which have the "Main-Node-Type" as a supertype. The CND of the main node-type looks like: [nt:GSBL] o