Hi,
On 07.06.2010 16:56, Justin Edelson wrote:
> On 6/7/10 10:45 AM, Carsten Ziegeler wrote:
>> Justin Edelson wrote
>>> And then move it to jcr.contentloader?
>> I think while contentloader is more an optional bundle, the namespace
>> prefix handling is more a required thing, therefore I would not move
>> this to the contentloader.
> I hadn't thought of contentloader being optional. In that context, I
> agree that nodetype and prefix loading is not a good match.
>
> I just find having classes named *Loader which aren't in the bundle
> called contentloader is non-intuitive. I think I still look in
> contentloader when I want to debug node type loading :)
>
> But loss of a few minutes every month isn't worth a breaking change :)
>
I agree with the name "Loader" not being a good one.
Currently I am working on a path along these lines:
* Split namespace and node type handling in two classes
* BundleNameSpaceMapper is a DS Component providing the
NamespaceMapper service reading maapings from the manifest
This is independent of any repository; and there is just
one instance per framework.
* NodeTypeRegistrar is managed by the AbstractSlingRepository,
it is related to the repository which controls it and
just manages node types and there is an instance for each
SlingRepository service.
The NodeTypeRegistrar should be the basis to enhance it to implement
SLING-7.
I think both should keep on living in the JCR Base bundle.
WDYT ?
Regards
Felix
