Triggered by the recent problems and proposals from Alexander Saar[1], I
thought a little bit about the ServiceLocator (again) :)
The reason for the existence of the service locator is to make the life
of script developers easier with respect to accessing OSGi services.
Currently, the locator i
Hi all,
Am Dienstag, den 26.02.2008, 14:52 +0100 schrieb Carsten Ziegeler:
> Triggered by the recent problems and proposals from Alexander Saar[1], I
> thought a little bit about the ServiceLocator (again) :)
>
> The reason for the existence of the service locator is to make the life
> of scrip
Felix Meschberger wrote:
Therefore I propose the following changes:
a) move the service locator to the scripting package
in the API ? I would leave the interface exactly where it is. IMHO there
is no reason to move this.
Yes, I thought of moving it from the o.a.s.api.services to the
o.a.s.api
On Tue, Feb 26, 2008 at 3:28 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> ... Yes, I thought of moving it from the o.a.s.api.services to the
> o.a.s.api.scripting package. ...
> ... But I'm fine with leaving it in a separate package as well ...
I agree with leaving it where it is, and agre
Hi,
Am Dienstag, den 26.02.2008, 15:28 +0100 schrieb Carsten Ziegeler:
> Felix Meschberger wrote:
> >> Therefore I propose the following changes:
> >> a) move the service locator to the scripting package
> >
> > in the API ? I would leave the interface exactly where it is. IMHO there
> > is no re
Felix Meschberger wrote:
Hi,
Am Dienstag, den 26.02.2008, 15:28 +0100 schrieb Carsten Ziegeler:
Felix Meschberger wrote:
Therefore I propose the following changes:
a) move the service locator to the scripting package
in the API ? I would leave the interface exactly where it is. IMHO there
is
I have created SLING-279 to track the progress of this issue.
Carsten
Carsten Ziegeler schrieb:
Felix Meschberger wrote:
Hi,
Am Dienstag, den 26.02.2008, 15:28 +0100 schrieb Carsten Ziegeler:
Felix Meschberger wrote:
Therefore I propose the following changes:
a) move the service locator to
If noone objects, I'll change sling according to SLING-279 by the end of
the week.
Carsten
Carsten Ziegeler wrote:
I have created SLING-279 to track the progress of this issue.
Carsten
Carsten Ziegeler schrieb:
Felix Meschberger wrote:
Hi,
Am Dienstag, den 26.02.2008, 15:28 +0100 schrieb
Sounds great.
I agree with the proposed changes. In fact I think anything that moves
efforts like providing such environment variables away from
application developers makes it easier to develop sling applications
and will help to reduce errors.
I have only one question that is due to my
Hi Alex,
Am Dienstag, den 26.02.2008, 17:57 +0100 schrieb Alexander Saar:
> I have only one question that is due to my limited knowledge of OSGI.
> Is there anything like a security concept that controls access to
> OSGI services? As far as I understand the proposed changes the service
> lo
> Hi Alex,
>
> Am Dienstag, den 26.02.2008, 17:57 +0100 schrieb Alexander Saar:
> > I have only one question that is due to my limited knowledge of OSGI.
> > Is there anything like a security concept that controls access to
> > OSGI services? As far as I understand the proposed changes the ser
So, ATM I'm able to access every service that is deployed into Sling,
regardless which BundleContext is used and in future there might be a
concept for mapping JCR user rights to OSGI service access, right? I
have currently no real use case in mind but I can imagine that such a
functionalit
On Thu, Feb 28, 2008 at 10:28 AM, Alexander Saar
<[EMAIL PROTECTED]> wrote:
> ...in future there might be a
> concept for mapping JCR user rights to OSGI service access, right?...
I'd make sure that's "in the future" and "if someone ever needs that" ;-)
I'm sure we have much more urgent things
Definitely.
Am 28.02.2008 um 10:36 schrieb Bertrand Delacretaz:
On Thu, Feb 28, 2008 at 10:28 AM, Alexander Saar
<[EMAIL PROTECTED]> wrote:
...in future there might be a
concept for mapping JCR user rights to OSGI service access, right?...
I'd make sure that's "in the future" and "if someon
14 matches
Mail list logo
