Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: ServiceFactory
From: Quinn Stevenson <quinn@pronoia-solutions.com>
In-Reply-To: 
 <CAA8i-pZNHVS0gB6trbMRVnvqGMfm7ajVJMBFA4VOpiKdzqe2KA@mail.gmail.com>
Date: Sat, 27 Feb 2016 13:02:14 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B5B758F7-B85B-42A7-A56E-C00E8A23C1A4@pronoia-solutions.com>
References: <1456521821859-5778336.post@n5.nabble.com>
 <CAA8i-pZmLT7DK66+mRa8Yqztf_iq=YOZxvMH+MZjy=w-qHoh1w@mail.gmail.com>
 <610CB59C-7D76-4321-BE67-CB7DDCFCB9E3@pronoia-solutions.com>
 <CAA8i-paWY1EP7FWTGfQZLk6fVbsAFCRPivPddu-9B07wasHauw@mail.gmail.com>
 <CAA8i-pZNHVS0gB6trbMRVnvqGMfm7ajVJMBFA4VOpiKdzqe2KA@mail.gmail.com>
To: users@camel.apache.org

I=E2=80=99m pretty sure that=E2=80=99s how the Blueprint proxy works.

You can use Blueprint to reference services exposed via pure OSGi, =
Declarative Services and Blueprint - all of them are proxied.  So the =
proxy would have to be on the caller, not the server.

You may be able to do what you=E2=80=99re after by registering a factory =
as a service, and then calling a method on your factory to return the =
object you want - just a thought.


> On Feb 27, 2016, at 12:56 PM, Brad Johnson =
<brad.johnson@mediadriver.com> wrote:
>=20
> Your observation about the caller being the proxied side is =
interesting.  I
> hadn't really thought about it before.  Conceptually I'd always =
assumed
> that it would be the registration that would proxy the
> interface/implementation and that whomever grabbed got that.  When the
> service would change then the proxy could stay the same but the =
internally
> delegated class would be different.  Interesting.
>=20
> On Sat, Feb 27, 2016 at 1:30 PM, Brad Johnson =
<brad.johnson@mediadriver.com>
> wrote:
>=20
>> I think you're right from what I'm seeing.  I'll probably have to =
resort
>> to an Activator and register the service. I'm just making this so =
that I
>> can change the cfg file and switch the internal implementation =
between
>> three different types: test, impl, or remote.  Test just serves up =
dummy
>> data, impl is what it sound like and remote is an implementation with =
a
>> ProducerTemplate that in turn delegates calls to URIs for easy
>> distribution.
>>=20
>> I can make that easy enough if I just use a Class.forName on a passed =
in
>> String and delegate to it but I'm trying to color within the lines.
>>=20
>> On Sat, Feb 27, 2016 at 1:18 PM, Quinn Stevenson <
>> quinn@pronoia-solutions.com> wrote:
>>=20
>>> I don=E2=80=99t believe the way the service is exposed has any =
bearing on when a
>>> proxy is created - the proxy is created by the <reference =E2=80=A6.>,=
 not the
>>> <service>
>>>=20
>>> Also, if you=E2=80=99re trying to achieve a service with the =
properties of an
>>> OSGi Service Factory (i.e. one service instance per calling bundle), =
I
>>> don=E2=80=99t think what you have will work - you=E2=80=99ll wind up =
with a single instance
>>> of the service in the container.  See this JIRA for a little more =
info as
>>> to why. https://issues.apache.org/jira/browse/KARAF-4284
>>> <https://issues.apache.org/jira/browse/KARAF-4284>
>>>=20
>>> <https://issues.apache.org/jira/browse/KARAF-4284?filter=3D-2>
>>>> On Feb 26, 2016, at 2:35 PM, Brad Johnson =
<brad.johnson@mediadriver.com>
>>> wrote:
>>>>=20
>>>> Just a quick follow up to that question, the class is not proxied =
in
>>> CBTS
>>>> but that may be an impedance mismatch between the test harness and =
an
>>>> actual OSGi container and not indicative of how it will be handled =
by
>>>> blueprint in Karaf.
>>>>=20
>>>> On Fri, Feb 26, 2016 at 3:23 PM, Ranx =
<brad.johnson@mediadriver.com>
>>> wrote:
>>>>=20
>>>>> If I create a service factory instantiated in blueprint like this:
>>>>>=20
>>>>>       <bean id=3D"service" class=3D"fo.bar.ServiceFactory"
>>>>> factory-method=3D"createService" >
>>>>>               <argument value=3D"${serviceClassImpl}"/>
>>>>>=20
>>>>>       </bean>
>>>>>       <service ref=3D"service" interface=3D"foo.api.MyOSGiService" =
/>
>>>>>=20
>>>>> And inside the factory just do a Class.forName to instantiate and
>>> return
>>>>> it,
>>>>> will the service reference itself be proxied?
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> --
>>>>> View this message in context:
>>>>> http://camel.465427.n5.nabble.com/ServiceFactory-tp5778336.html
>>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>>>=20
>>>=20
>>>=20
>>=20