Rich,

If you use <implementation.osgi/> with OSGi declarative services to wire
references, SCA installs proxies for the remote services into the OSGi
registry. On each JVM, the OSGi references will get wired to the SCA
proxies, enabling multiple services and reference from different nodes to be
wired in a distributed SCA runtime. We dont currently have a sample for this
usage, but you could take a look at the webservice test in
itest/osgi-implementation.


On 8/22/08, Rich Smith (rjsmith2) <[EMAIL PROTECTED]> wrote:
>
>  Hi, Rajini.  That approach sounds fine.
>
> A question I have then is how to use a distributed SCA runtime (multiple
> nodes) where
> each node is running OSGi.  If SCA is not wiring references, then how would
> a service
> in one JVM get injected references from another JVM?
>
>      --Rich
>
>
>  ------------------------------
> *From:* Rajini Sivaram [mailto:[EMAIL PROTECTED]
> *Sent:* Friday, August 22, 2008 11:35 AM
> *To:* [email protected]
> *Subject:* Re: Question on OSGi implementation, service wiring, Spring DM
>
>
>  Rich,
>
> osgi-supplychain uses <implementation.osgi/> which enables applications
> using the OSGi programming model to be included in a SCA composition. If you
> wish to use reference injection, you can use OSGi declarative services.
> There is a sample in the same directory samples/osgi-supplychain which uses
> DS.
>
> We dont support SCA reference injection with OSGi components using
> <implementation.osgi/> because OSGi is a far more dynamic environment.
>
>
> On 8/4/08, Rich Smith (rjsmith2) <[EMAIL PROTECTED]> wrote:
>>
>>  Is the osgi-supplychain example current?
>>
>> The reason I ask is that it requires all bundles to use a standard
>> BundleActivator
>> that wires the service references, instead of having the Tuscany OSGi
>> implementation
>> wire the references using a bundle listener.  (It also doesn't use
>> ServiceTracker, but
>> I don't know if that's due to some implementation constraint.)
>>
>> I want to know if this has changed.  The OSGi implementation should wire
>> the
>> references from the implementation bundle without requiring the wiring
>> logic in all of
>> the component bundles.  This example, as-is, really violates the SCA IoC
>> principle
>> since it requires components to wire their own references rather than
>> having them
>> injected.
>>
>> Also, I'd like to second the question that another user asked about
>> whether or not
>> there are any plans to use Spring DM to wire service references across
>> bundles.
>>
>> We would definitely like to have Spring DM integration with OSGi for our
>> application.
>>
>> Spring DM integration would definitely solve the service wiring problem,
>> as well as
>> providing important support for OSGi-based web applications, plus just
>> generally
>> Spring integration in an OSGi environment.
>>
>> Without Spring DM, our application can't use the OSGi implementation.
>>
>> Please advise.
>>
>> Also, if any Tuscany developers feel that these things are missing, but
>> don't have
>> the bandwidth or plans to add them, please reply to me offline about the
>> difficulty
>> level of doing this, and where to get started, etc.
>>
>>      --Rich
>>
>>
>
>
>
> --
> Thank you...
>
> Regards,
>
> Rajini
>



-- 
Thank you...

Regards,

Rajini

Reply via email to