Hi, Am Mittwoch, den 12.03.2008, 07:56 +0100 schrieb Bertrand Delacretaz: > On Tue, Mar 11, 2008 at 7:59 PM, Vidar Ramdal <[EMAIL PROTECTED]> wrote: > > > ...It seems Sling attempts to register nodetypes on every startup, even > > though they're already be registered - and when registering fails, > > Sling gives up on trying to connect to the repository. This is a bit > > odd, right?... > > I agree, to be usable with any JCR repository (and that might improve > the situation when using Jackrabbit over RMI), Sling should IMHO use > the following rules to define a node type > > a) Test if the nodetype is already defined, using the JCR APIs > > b) If not defined, try to define it. Currently this requires using > Jackrabbit-specific APIs as JSR 170 does not provide this. > > c) If that fails, log a warning but do not prevent connecting to the > JCR repository. People should manually register the required nodetypes > if Sling cannot do that automatically, so the warning message must > include precise info on what needs to be registered. > > What do people think?
SLING-7 ;-) This is in fact one of our oldest unfixed issues ... Regards Felix
