aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alasdair Nottingham <>
Subject Re: JNDI and proxying
Date Fri, 09 Jul 2010 20:21:42 GMT
I'm still a little concerned about this. I have two concerns:

1. How does the client deal with the dynamism in the non-proxies case.
2. How does the client know whether they have a non-proxied object so it can be treated differently.

I'm a little concerned that the client needs to act differently in the proxied vs non-proxied

Alasdair Nottingham

On 9 Jul 2010, at 14:03, Lin Sun <> wrote:

> I like the idea too!  I had been wondering how we could differentiate
> the case where we absolutely want the proxy generated vs the case
> where we want a non-proxies service object returned when we cannot
> proxy the class.
> Lin
> On Thu, Jul 8, 2010 at 11:54 PM, Jarek Gawor <> wrote:
>> No, that would violate the OSGi JNDI spec. The Aries JNDI
>> implementation actually supports two url schemes for looking up
>> services via jndi: the standard one - "osgi:service/" and non-standard
>> one - "aries:services/". Right now both work in exactly the same way.
>> But we could modify things a bit so that when "aries:services/" scheme
>> it could return a non-proxied service object (when proxying fails).
>> Jarek

View raw message