equinox-dev http://dev.eclipse.org/mhonarc/lists/equinox-dev/maillist.html equinox-dev en-us Wed, 18 Nov 2009 15:51:23 GMT Wed, 18 Nov 2009 15:51:23 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) equinox-dev http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/equinox-dev/maillist.html Re: [equinox-dev] Registering two services in the same bundle http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05958.html David, While Thomas's suggestion is absolutely correct, I think you need to step back from the problem a little and ask if this is the right approach. If your consumer bundle needs the Interface1 service then it should simply bind to an instance of Interf... You should keep in mind the different views of the service between the registrant and the consumer. On the registrant (service producing/implementing) side, it is perfectly reasonable for them to register a single service object under all the different service interfaces they implement. But I think Niel's point is on the side of the consumer bundle. I think it is far more simple for them to simply bind to each service (interface) that they require individually instead of trying to find a particular service which implements all the service interfaces they need at once and then casting that single service to the various interfaces it implements. As Neil points out this also couples a client to a particular type of implementation that must use a single service registration for all the service interfaces needed by the client.

Tom



Inactive hide details for Tim Diekmann ---11/16/2009 05:46:21 PM---Neil, one concrete example where the services need to be proTim Diekmann ---11/16/2009 05:46:21 PM---Neil, one concrete example where the services need to be provided as a unit is the support for JTA (coming in the Enterprise Pr


From:
Tim Diekmann <tdiekman@xxxxxxxxx>

To:
"Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>

Date:
11/16/2009 05:46 PM

Subject:
Re: [equinox-dev] Registering two services in the same bundle



Neil,

one concrete example where the services need to be provided as a unit is the support for JTA (coming in the Enterprise Profile soon). In the JTA case, the provider is mandated to implement 3 services and register them, among them UserTransaction and TransactionManager. Since they come from the JTA spec, they cannot be easily combined.

Tim.

"In the end everything will be right. But since things are not right, we are not at the end yet!"
-- Unknown



On Nov 16, 2009, at 3:32 PM, Neil Bartlett wrote:
      David,

      While Thomas's suggestion is absolutely correct, I think you need to step back from the problem a little and ask if this is the right approach.

      If your consumer bundle needs the Interface1 service then it should simply bind to an instance of Interface1. If it also needs the Interface2 service then it should just bind to Interface2. The consumer should not *require* both services to be offered by the same object, because this will severely limit the ability of other producers to offer an alternative implementation for those services. In other words, you are coupling your consumer to an implementation detail of the producer which it shouldn't care about.

      On the other hand, if your API is such that these interfaces really should be published and consumed as a unit, then maybe you should just merge them into one interface, or declare a new Interface3 that extends both Interface1 and Interface2.

      Neil
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


GIF image

GIF image

]]> Wed, 18 Nov 2009 15:42:59 GMT http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05958.html tjwatson@xxxxxxx (Thomas Watson) [equinox-dev] How to manage SIP Servlet as a bundle in OSGI platform http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05957.html Dear: I just started studying and using OSGI,and I found that osgi support deploying the Http Service into the platform as a bundle, depending on the org.eclipse.equinox.http bundle that just like the web container.; I wonder whether the osgi also support...
Dear:
I just started studying and using OSGI,and I found that osgi support deploying the Http Service into the platform as a bundle, depending on the org.eclipse.equinox.http bundle that just like the web container. 
I wonder whether the osgi also support the SIP Service,I want to deploy the SIP Servlet into the OSGI as a bundle ,and how to do. Thank you.
 
Best Regards
 
 
 
 
2009-11-18
Fox Su 
 ]]> Wed, 18 Nov 2009 13:09:17 GMT http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05957.html sjrfox@xxxxxxx (苏晋荣) Re: [equinox-dev] attach a fragment in runtime http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05956.html Equinox Thomas Watson wrote: > > >>That console output does not look familiar to me. Is that from the Equinox >>console? > > No, it's a knopflerfish console > thank you for replying. > > > > |------------> > | From: | > |------------> > > >--------------------------------------------------------------------------------------------------------------------------------------------------| > |prof_trg <prof.target@xxxxxxxxx> > | > > >--------------------------------------------------------------------------------------------------------------------------------------------------| > |------------> > | To: | > |------------> > > >--------------------------------------------------------------------------------------------------------------------------------------------------| > |equinox-dev@xxxxxxxxxxx > | > > >--------------------------------------------------------------------------------------------------------------------------------------------------| > |------------> > | Date: | > |------------> > > >--------------------------------------------------------------------------------------------------------------------------------------------------| > |10/08/2009 03:53 PM > | > > >--------------------------------------------------------------------------------------------------------------------------------------------------| > |------------> > | Subject: | > |------------> > > >--------------------------------------------------------------------------------------------------------------------------------------------------| > |[equinox-dev] attach a fragment in runtime > | > > >--------------------------------------------------------------------------------------------------------------------------------------------------| > > > > > > > Hello, > I am trying to attach a fragment to its host at runtime, but I have some > issues... > in fact , I uninstall the fragment then I install it again, but as if it > is > not detected by the host... > > before uninstalling the fragment, I have this line in my console: > > 29 2/active Host (h:28) > 28 2/resolved Fragment (f:29) > > after uninstalling and then installing the fragment again : > > 29 2/active Host (h:28) > 30 2/installed Fragment > > would someone help me understanding this? > Regard > -- > View this message in context: > http://www.nabble.com/attach-a-fragment-in-runtime-tp25810711p25810711.html > Sent from the Equinox - Dev mailing list archive at Nabble.com. > > _______________________________________________ > equinox-dev mailing list > equinox-dev@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > > > > _______________________________________________ > equinox-dev mailing list > equinox-dev@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > -- View this message in context: http://old.nabble.com/attach-a-fragment-in-runtime-tp25810711p26392026.html Sent from the Equinox - Dev mailing list archive at Nabble.com. ]]> Tue, 17 Nov 2009 15:38:48 GMT http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05956.html prof.target@xxxxxxx (prof_trg) RE: [equinox-dev] Registering two services in the same bundle http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05955.html Hi Thomas, Thank you for your answer, So once I get ServiceReference = X getServiceReferences using the filter that you told me &quot;(&amp;(objectClass=Interface1)(objectClass=Interface2))&quot;, I have to use two castings for getting two different services like O...

Hi Neil,

 

Thank you for your answer,

 

I agree with you, in the final deployment, I should not be able to get two interfaces from the same object because in this case it would better to merge them in another interface3 as you said, I just wanted to ask the different ways to do that.

 

 

David

 

De: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] En nombre de Neil Bartlett
Enviado el: martes, 17 de noviembre de 2009 0:32
Para: Equinox development mailing list
Asunto: Re: [equinox-dev] Registering two services in the same bundle

 

David,

 

While Thomas's suggestion is absolutely correct, I think you need to step back from the problem a little and ask if this is the right approach.

 

If your consumer bundle needs the Interface1 service then it should simply bind to an instance of Interface1. If it also needs the Interface2 service then it should just bind to Interface2. The consumer should not *require* both services to be offered by the same object, because this will severely limit the ability of other producers to offer an alternative implementation for those services. In other words, you are coupling your consumer to an implementation detail of the producer which it shouldn't care about.

 

On the other hand, if your API is such that these interfaces really should be published and consumed as a unit, then maybe you should just merge them into one interface, or declare a new Interface3 that extends both Interface1 and Interface2.

 

Neil

On Mon, Nov 16, 2009 at 3:38 PM, David Conde <dconde@xxxxxxxx> wrote:

Hi Thomas,

 

Thank you for your answer,

 

So once I get ServiceReference = X getServiceReferences using the filter that you told me "(&(objectClass=Interface1)(objectClass=Interface2))", I have to use two castings for getting two different services like Object1 = (Interface1) BundleContext.getReference (X) and Object2= (Interface2) BundleContext.getReference(X), and then use two instances of the same object for using two different interfaces implemented by this same object, am I right? Is there any other mechanism for using the same object for two different interfaces, because really the object provides two different services (2 different interfaces)

 

Thank you in advance

 

David

 

De: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] En nombre de Thomas Watson
Enviado el: lunes, 16 de noviembre de 2009 15:53
Para: Equinox development mailing list
Asunto: Re: [equinox-dev] Registering two services in the same bundle

 

You can use the registerService(java.lang.String[] clazzes,java.lang.Object service, java.util.Dictionary properties) to register your service object under multiple service interfaces. This will allow you to control the registration with a single ServiceRegistration object. But in order to get a ServiceReference that is guaranteed to implement both service interfaces then you must use the getServiceReferences(String clazz, String filter) with a null clazz and a filter that looks something like this:

"(&(objectClass=Interface1)(objectClass=Interface2))"

This will ensure that the ServiceReference objects returned implement both Interface1 and Interface2. This should allow you to cast the Object returned from getService(ServiceReference) to both Interface1 and Interface2 in your service using client bundle. But for client code I recommend you use an injection mechanism (like Declarative Services, Spring DM or Blueprint) if possible so you don't have to worry about tracking the services yourself.

Tom



Inactive hide details for "David Conde" ---11/16/2009 02:34:18 AM---Hi,"David Conde" ---11/16/2009 02:34:18 AM---Hi,


From:


"David Conde" <dconde@xxxxxxxx>


To:


"'Equinox development mailing list'" <equinox-dev@xxxxxxxxxxx>


Date:


11/16/2009 02:34 AM


Subject:


[equinox-dev] Registering two services in the same bundle




Hi,

I would like to know what I have to do for registering two different services in a same bundle. I mean, I have two create a service object which implements two different interfaces (registering two different services). I thought about using registerService(java.lang.String[] clazzes,java.lang.Object service,
java.util.Dictionary properties) by including Interface1.class.getName() and Interface2.class.getName() in String array called clazzes.

However, I found as a problem that if I want to use this object service I have to get two service objects, one for Interface1 and another one for Interface2 by doing BundleContext.getServiceReference(Interface1) & BundleContext.getServiceReference(Interface2), am I missing anything?Does it exist another way to do that?

Thanks in advance _______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

 

GIF image

PNG image

PNG image

]]> Tue, 17 Nov 2009 07:55:14 GMT http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05955.html dconde@xxxxxxx (David Conde) Re: [equinox-dev] Registering two services in the same bundle http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05954.html Neil,one concrete example where the services need to be provided as a unit is the support for JTA (coming in the Enterprise Profile soon). In the JTA case, the provider is mandated to implement 3 services and register them, among them UserTransaction and T... Neil,

one concrete example where the services need to be provided as a unit is the support for JTA (coming in the Enterprise Profile soon). In the JTA case, the provider is mandated to implement 3 services and register them, among them UserTransaction and TransactionManager. Since they come from the JTA spec, they cannot be easily combined.

   Tim.

"In the end everything will be right. But since things are not right, we are not at the end yet!"
   -- Unknown



On Nov 16, 2009, at 3:32 PM, Neil Bartlett wrote:

David,

While Thomas's suggestion is absolutely correct, I think you need to step back from the problem a little and ask if this is the right approach.

If your consumer bundle needs the Interface1 service then it should simply bind to an instance of Interface1. If it also needs the Interface2 service then it should just bind to Interface2. The consumer should not *require* both services to be offered by the same object, because this will severely limit the ability of other producers to offer an alternative implementation for those services. In other words, you are coupling your consumer to an implementation detail of the producer which it shouldn't care about.

On the other hand, if your API is such that these interfaces really should be published and consumed as a unit, then maybe you should just merge them into one interface, or declare a new Interface3 that extends both Interface1 and Interface2.

Neil

]]> Mon, 16 Nov 2009 23:46:06 GMT http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05954.html tdiekman@xxxxxxx (Tim Diekmann) [equinox-dev] Equinox tagged for the next Helios integration build. http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05953.html The map file has been updated for the following Bug changes: The following projects have changed: org.eclipse.equinox.launcher.win32.win32.ia64 org.eclipse.equinox.launcher.releng org.eclipse.equinox.launcher.carbon.macosx org.eclipse.equinox.launcher.win... The map file has been updated for the following Bug changes:
+ Bug 244468. Support reading extension registry in any locale (FIXED)
+ Bug 275379. [launcher] Native Launcher looks for shared library in nl fragment (FIXED)
+ Bug 291919. [launcher] return different error codes when failing to start java (FIXED)
+ Bug 293831. [launcher] AIX needs jre/lib/<arch> on library search path (ASSIGNED)
+ Bug 293840. [launcher] AIX build of eclipse binary needs adjusting. (FIXED)

The following projects have changed:
org.eclipse.equinox.launcher.win32.win32.ia64
org.eclipse.equinox.launcher.releng
org.eclipse.equinox.launcher.carbon.macosx
org.eclipse.equinox.launcher.win32.win32.x86_64
org.eclipse.equinox.launcher.gtk.linux.ppc
org.eclipse.equinox.launcher.gtk.solaris.x86
org.eclipse.equinox.launcher.motif.solaris.sparc
org.eclipse.equinox.launcher.motif.linux.x86
org.eclipse.equinox.launcher.gtk.linux.x86_64
org.eclipse.equinox.launcher.cocoa.macosx.x86_64
org.eclipse.equinox.launcher.motif.hpux.ia64_32
org.eclipse.equinox.launcher.wpf.win32.x86
org.eclipse.equinox.launcher.cocoa.macosx
org.eclipse.equinox.launcher
org.eclipse.equinox.launcher.win32.win32.x86
org.eclipse.equinox.executable
org.eclipse.equinox.launcher.gtk.solaris.sparc
org.eclipse.equinox.launcher.motif.aix.ppc
org.eclipse.equinox.common
org.eclipse.equinox.launcher.gtk.linux.x86

Tom

]]> Mon, 16 Nov 2009 23:45:07 GMT http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05953.html tjwatson@xxxxxxx (Thomas Watson) Re: [equinox-dev] Registering two services in the same bundle http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05952.html
While Thomas's suggestion is absolutely correct, I think you need to step back from the problem a little and ask if this is the right approach.

If your consumer bundle needs the Interface1 service then it should simply bind to an instance of Interface1. If it also needs the Interface2 service then it should just bind to Interface2. The consumer should not *require* both services to be offered by the same object, because this will severely limit the ability of other producers to offer an alternative implementation for those services. In other words, you are coupling your consumer to an implementation detail of the producer which it shouldn't care about.

On the other hand, if your API is such that these interfaces really should be published and consumed as a unit, then maybe you should just merge them into one interface, or declare a new Interface3 that extends both Interface1 and Interface2.

Neil

On Mon, Nov 16, 2009 at 3:38 PM, David Conde <dconde@xxxxxxxx> wrote:

Hi Thomas,

Â

Thank you for your answer,

Â

So once I get ServiceReference = X getServiceReferences using the filter that you told me "(&(objectClass=Interface1)(objectClass=Interface2))", I have to use two castings for getting two different services like Object1 = (Interface1) BundleContext.getReference (X) and Object2= (Interface2) BundleContext.getReference(X), and then use two instances of the same object for using two different interfaces implemented by this same object, am I right? Is there any other mechanism for using the same object for two different interfaces, because really the object provides two different services (2 different interfaces)

Â

Thank you in advance

Â

David

Â

De: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] En nombre de Thomas Watson
Enviado el: lunes, 16 de noviembre de 2009 15:53
Para: Equinox development mailing list
Asunto: Re: [equinox-dev] Registering two services in the same bundle

Â

You can use the registerService(java.lang.String[] clazzes,java.lang.Object service, java.util.Dictionary properties) to register your service object under multiple service interfaces. This will allow you to control the registration with a single ServiceRegistration object. But in order to get a ServiceReference that is guaranteed to implement both service interfaces then you must use the getServiceReferences(String clazz, String filter) with a null clazz and a filter that looks something like this:

"(&(objectClass=Interface1)(objectClass=Interface2))"

This will ensure that the ServiceReference objects returned implement both Interface1 and Interface2. This should allow you to cast the Object returned from getService(ServiceReference) to both Interface1 and Interface2 in your service using client bundle. But for client code I recommend you use an injection mechanism (like Declarative Services, Spring DM or Blueprint) if possible so you don't have to worry about tracking the services yourself.

Tom



Inactive hide details for "David Conde" ---11/16/2009 02:34:18 AM---Hi,"David Conde" ---11/16/2009 02:34:18 AM---Hi,


From:


"David Conde" <dconde@xxxxxxxx>


To:


"'Equinox development mailing list'" <equinox-dev@xxxxxxxxxxx>


Date:


11/16/2009 02:34 AM


Subject:


[equinox-dev] Registering two services in the same bundle




Hi,

I would like to know what I have to do for registering two different services in a same bundle. I mean, I have two create a service object which implements two different interfaces (registering two different services). I thought about using registerService(java.lang.String[] clazzes,java.lang.Object service,
java.util.Dictionary properties) by including Interface1.class.getName() and Interface2.class.getName() in String array called clazzes.

However, I found as a problem that if I want to use this object service I have to get two service objects, one for Interface1 and another one for Interface2 by doing BundleContext.getServiceReference(Interface1) & BundleContext.getServiceReference(Interface2), am I missing anything?Does it exist another way to do that?

Thanks in advance _______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


GIF image

PNG image

PNG image

]]> Mon, 16 Nov 2009 23:32:09 GMT http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05952.html njbartlett@xxxxxxx (Neil Bartlett) [equinox-dev] Tagged core.* and Equinox for Helios stream build http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05951.html The map file has been updated for the following Bug changes: registry in any locale (FIXED) only sets exec bit for owner. (ASSIGNED) workspace refresh due to FileInfo carrying substring baggage (FIXED) The following projects have changed: org.eclipse.core... The map file has been updated for the following Bug changes:
+ Bug 244468. Support reading extension registry in any locale (FIXED)
+ Bug 259643. LocalFileNatives.internalSetFileInfo only sets exec bit for owner. (ASSIGNED)
+ Bug 294429. OutOfMemoryError during workspace refresh due to FileInfo carrying substring baggage (FIXED)

The following projects have changed:
org.eclipse.core.runtime.compatibility.registry
org.eclipse.core.tests.runtime
org.eclipse.core.filesystem
org.eclipse.equinox.registry
org.eclipse.core.filesystem.linux.x86

]]> Mon, 16 Nov 2009 23:16:02 GMT http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05951.html John_Arthorne@xxxxxxx (John Arthorne) RE: [equinox-dev] Registering two services in the same bundle http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05950.html Hi, Yes you can simply get the service once and cast it to the two types you want: Object someService = bc.getService(x); Interface1 service1 = (Interface1) someService; Interface2 service2 = (Interface2) someService; Tom &quot;David Conde&quot; ---11/16/2009 09:34... Hi,

Yes you can simply get the service once and cast it to the two types you want:

Object someService = bc.getService(x);
Interface1 service1 = (Interface1) someService;
Interface2 service2 = (Interface2) someService;

Tom



Inactive hide details for "David Conde" ---11/16/2009 09:34:35 AM---Hi Thomas,"David Conde" ---11/16/2009 09:34:35 AM---Hi Thomas,


From:
"David Conde" <dconde@xxxxxxxx>

To:
"'Equinox development mailing list'" <equinox-dev@xxxxxxxxxxx>

Date:
11/16/2009 09:34 AM

Subject:
RE: [equinox-dev] Registering two services in the same bundle



Hi Thomas,

Thank you for your answer,

So once I get ServiceReference = X getServiceReferences using the filter that you told me "(&(objectClass=Interface1)(objectClass=Interface2))", I have to use two castings for getting two different services like Object1 = (Interface1) BundleContext.getReference (X) and Object2= (Interface2) BundleContext.getReference(X), and then use two instances of the same object for using two different interfaces implemented by this same object, am I right? Is there any other mechanism for using the same object for two different interfaces, because really the object provides two different services (2 different interfaces)

Thank you in advance

David

De: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] En nombre de Thomas Watson
Enviado el: lunes, 16 de noviembre de 2009 15:53
Para: Equinox development mailing list
Asunto: Re: [equinox-dev] Registering two services in the same bundle

You can use the registerService(java.lang.String[] clazzes,java.lang.Object service, java.util.Dictionary properties) to register your service object under multiple service interfaces. This will allow you to control the registration with a single ServiceRegistration object. But in order to get a ServiceReference that is guaranteed to implement both service interfaces then you must use the getServiceReferences(String clazz, String filter) with a null clazz and a filter that looks something like this:

"(&(objectClass=Interface1)(objectClass=Interface2))"

This will ensure that the ServiceReference objects returned implement both Interface1 and Interface2. This should allow you to cast the Object returned from getService(ServiceReference) to both Interface1 and Interface2 in your service using client bundle. But for client code I recommend you use an injection mechanism (like Declarative Services, Spring DM or Blueprint) if possible so you don't have to worry about tracking the services yourself.

Tom



Inactive hide details for "David Conde" ---11/16/2009 02:34:18 AM---Hi,"David Conde" ---11/16/2009 02:34:18 AM---Hi,


From:
"David Conde" <dconde@xxxxxxxx>

To:
"'Equinox development mailing list'" <equinox-dev@xxxxxxxxxxx>

Date:
11/16/2009 02:34 AM

Subject:
[equinox-dev] Registering two services in the same bundle





Hi,

I would like to know what I have to do for registering two different services in a same bundle. I mean, I have two create a service object which implements two different interfaces (registering two different services). I thought about using registerService(java.lang.String[] clazzes,java.lang.Object service,
java.util.Dictionary properties) by including Interface1.class.getName() and Interface2.class.getName() in String array called clazzes.

However, I found as a problem that if I want to use this object service I have to get two service objects, one for Interface1 and another one for Interface2 by doing BundleContext.getServiceReference(Interface1) & BundleContext.getServiceReference(Interface2), am I missing anything?Does it exist another way to do that?

Thanks in advance _______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


GIF image

GIF image

GIF image

GIF image

]]> Mon, 16 Nov 2009 16:24:10 GMT http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05950.html tjwatson@xxxxxxx (Thomas Watson) RE: [equinox-dev] Registering two services in the same bundle http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05949.html Hi Thomas, Thank you for your answer, So once I get ServiceReference = X getServiceReferences using the filter that you told me &quot;(&amp;(objectClass=Interface1)(objectClass=Interface2))&quot;, I have to use two castings for getting two different services like O...

Hi Thomas,

 

Thank you for your answer,

 

So once I get ServiceReference = X getServiceReferences using the filter that you told me "(&(objectClass=Interface1)(objectClass=Interface2))", I have to use two castings for getting two different services like Object1 = (Interface1) BundleContext.getReference (X) and Object2= (Interface2) BundleContext.getReference(X), and then use two instances of the same object for using two different interfaces implemented by this same object, am I right? Is there any other mechanism for using the same object for two different interfaces, because really the object provides two different services (2 different interfaces)

 

Thank you in advance

 

David

 

De: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] En nombre de Thomas Watson
Enviado el: lunes, 16 de noviembre de 2009 15:53
Para: Equinox development mailing list
Asunto: Re: [equinox-dev] Registering two services in the same bundle

 

You can use the registerService(java.lang.String[] clazzes,java.lang.Object service, java.util.Dictionary properties) to register your service object under multiple service interfaces. This will allow you to control the registration with a single ServiceRegistration object. But in order to get a ServiceReference that is guaranteed to implement both service interfaces then you must use the getServiceReferences(String clazz, String filter) with a null clazz and a filter that looks something like this:

"(&(objectClass=Interface1)(objectClass=Interface2))"

This will ensure that the ServiceReference objects returned implement both Interface1 and Interface2. This should allow you to cast the Object returned from getService(ServiceReference) to both Interface1 and Interface2 in your service using client bundle. But for client code I recommend you use an injection mechanism (like Declarative Services, Spring DM or Blueprint) if possible so you don't have to worry about tracking the services yourself.

Tom



Inactive hide details for "David Conde" ---11/16/2009 02:34:18 AM---Hi,"David Conde" ---11/16/2009 02:34:18 AM---Hi,


From:


"David Conde" <dconde@xxxxxxxx>


To:


"'Equinox development mailing list'" <equinox-dev@xxxxxxxxxxx>


Date:


11/16/2009 02:34 AM


Subject:


[equinox-dev] Registering two services in the same bundle




Hi,

I would like to know what I have to do for registering two different services in a same bundle. I mean, I have two create a service object which implements two different interfaces (registering two different services). I thought about using registerService(java.lang.String[] clazzes,java.lang.Object service,
java.util.Dictionary properties) by including Interface1.class.getName() and Interface2.class.getName() in String array called clazzes.

However, I found as a problem that if I want to use this object service I have to get two service objects, one for Interface1 and another one for Interface2 by doing BundleContext.getServiceReference(Interface1) & BundleContext.getServiceReference(Interface2), am I missing anything?Does it exist another way to do that?

Thanks in advance _______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

GIF image

PNG image

PNG image

]]> Mon, 16 Nov 2009 15:34:12 GMT http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg05949.html dconde@xxxxxxx (David Conde)