Hi, Am Mittwoch, den 12.03.2008, 00:52 -0700 schrieb Tobias Bocanegra: > > We don't check, because we don't parse the CND files and don't know > > which node types to check for ... > this is a big problem of the nt registering in jackrabbit. i would > like to have 2 flags. one that > automatically reregisters existing nodetypes if they differ, and > another that ignores existing nodetypes in the CND.
That would be great. Even better exceptions would help alot: Currently I parse the message to get at failure reason and to not log exceptions due to duplicate node type definitions.... > another option would be to expose the internal nodetype def builder > and decouple the CND parsing completely from registration. afaik this > is more or less what JSR283 suggests. That would even be better ... But still I would have some node type definition files, which would have to be parsed. > ps: i've rewritten/copied the CND parser now a couple of times, so > maybe i can provide at least a reassembler that cuts out those > nodetypes that are already registered in the repository. In a first attempt at approaching SLING-7 I tried to extract the CND parser out of the Jackrabbit code - but as there where so many core dependencies it just was not possible in a reasonable time frame ... Regards Felix
