On Apr 18, 2008, at 11:54 , Niklas Gustavsson wrote:
I got a requirement to be able to selectably expose OSGi services as a
SOAP based web service. My current thinking is to use a extender
bundle that interrogates other installed bundles for services declared
to be a web service. A service would be declared for web service
exposure using [...] service properties.
This is what we have done for "remoting" OSGi services (either as SOAP
or REST services or even JMX mbeans). The remoting bundle just listens
for services with either a property (or you can even use @annotations
if you don't mind running on at least Java 5).
[...] since web service frameworks are quite good at exposing Java
classes directly
I'm thinking I prefer the former model.
Agreed.
Greetings, Marcel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
