First, thanks.

I've just had a look to the link on Knopflerfish, and it seems to bring a
main part of what i'm looking for. It seems to go in the direction i imagine
: a service just delegates the soap work to the soap bundle. And using
service registering with properties seems a quite good way to make the link
between the bundles.

Before i give you a more complete opinion, i'll download this bundle. But,
according to the presentation page, i think some things perhaps are missing.

More parameters should be transmitted, through service registration, to make
the service generation a bit more flexible : choose the style and use (rpc,
document, etc.), give the namespaces, port and type name, etc...

Thanks again. Your comments are obviously welcome.
--
Ephemeris Lappis

>>> -----Original Message-----
>>> From: Tom [mailto:[EMAIL PROTECTED]
>>> Sent: Friday, June 17, 2005 6:26 PM
>>> To: Ephemeris Lappis
>>> Cc: Axis-User; Oscar
>>> Subject: Re: [oscar] AXIS in OSCAR
>>>
>>>
>>> Also, have you looke at "The Knopflerfish Axis Port"
>>> https://www.knopflerfish.org/svn/knopflerfish.org/trunk/osgi/bun
>>> dles_opt/soap/readme.html
>>>
>>> Please let us know if this does what you want to do.
>>>
>>>
>>> Ephemeris Lappis wrote:
>>>
>>> > Hello.
>>> >
>>> > I've been testing how to build an osgi bundle for soap web
>>> services, relying
>>> > on Axis...
>>> >
>>> > In a first time, a bundle can easily provide the full
>>> axis/jax-rpc libraries
>>> > and the web service implementation classes. With a simple
>>> HttpContext to
>>> > retrieve the axis wsdd descriptors, it seems to work...
>>> >
>>> > This first solution design is quite poor, since each new
>>> webservice should
>>> > include a full web services stack. I suppose a better design
>>> may provide a
>>> > generic soap/axis bundle, exposing a service for other bundles to
>>> > deploy/undeploy individual web-services, in a similar style
>>> the xml-rpc
>>> > bundle works.
>>> >
>>> > But this seems a bit more complex, and, wisely (?) i though
>>> perhaps somebody
>>> > had already worked on this, and avoid making twice the same things.
>>> >
>>> > So, is there anyone in this case ?
>>> >
>>> > --
>>> > Ephemeris Lappis
>>> >
>>> >
>>> >
>>> >
>>> >
>>> ------------------------------------------------------------------------
>>> >
>>> >
>>> > --
>>> > You receive this message as a subscriber of the
>>> [EMAIL PROTECTED] mailing list.
>>> > To unsubscribe: mailto:[EMAIL PROTECTED]
>>> > For general help: mailto:[EMAIL PROTECTED]
>>> > ObjectWeb mailing lists service home page:
>>> http://www.objectweb.org/wws

Reply via email to