Hi,
Am 25.02.2008 um 10:49 schrieb Carsten Ziegeler:
In a short chat with Carsten about that he proposed to move the
ServiceLocatorImpl into the sling scripting bundle so that other
bundles can
access the implementation and thus create their own service
locator. What do
others think about that?
BTW, I'm not sure if this is intended but sling already contains
two equal
implementation of the ServiceLocator interface that only differ in
the
package name. One in the core and one in the scheduler bundle.
Yes, this is intentional :) We didn't want to have a dependency from
the scheduler
to the core just because of code reuse for one single small class.
We could move this to a commons module if it makes sense.
But I think copying it for now isn't that bad, so we could just copy
it to the scripting bundle as well.
I agree that having a dependency to the core just to use some small
utilities is not the way to go. But since it is what it is, just a
small utility which is useful in many places, I think it would be
better to move this to the commons project instead of copying it again
and again.
- Alex
