Thanks for the link. I will have a look... As i said before, my first idea was to test how easy is to deploy a given web service using explicitly Axis. My first tests show it's quite easy to start the AxisEngine using the default HttpService with a simple http context. Now, i'm thinking about the better solution to provide a kind of SOAP server service, in the style of the existing XML-RPC service. The first solution, that i imagine not too much difficult (?), is to provide a specific Axis service that other bundles could invoke to deploy their services using the common wsdd descriptor. If i'm not mistaken, the problem in this first case will be to link the axis bundle classpath and the service bundle's packaged classes. This solution's main drawback is to provide an Axis service and not a generic SOAP service. The second, and ideal solution should be a pure SOAP service, although it relies on Axis implementation, for instance. A client service in this case could invoke it with the WSDL file, and some metadata parameter, and let it generate all the server classes. This dynamic generation seems quite more difficult and requires more much intrusion in the Axis process. Furthermore i'd need some help to achieve such an implementation... So, at last, i'd like to have your opinions about these solutions. Thanks again. -- Ephemeris Lappis
>>> -----Original Message----- >>> From: Peter Kriens [mailto:[EMAIL PROTECTED] >>> Sent: Friday, June 17, 2005 5:54 PM >>> To: Ephemeris Lappis >>> Cc: Axis-User; Oscar >>> Subject: Re: [oscar] AXIS in OSCAR >>> >>> >>> I think there is some SOAP stuff in the UPnP implementation of >>> Cybergarage that was very well refactored. Last time I looked it >>> seemed quite easy to turn the different layers into bundles: SOAP, >>> GENA, SSDP, HTTP. >>> >>> http://www.cybergarage.org/net/upnp/java/index.html >>> >>> Kind regards, >>> >>> Peter Kriens >>> >>> >>> EL> Hello. >>> >>> EL> I've been testing how to build an osgi bundle for soap web >>> services, relying >>> EL> on Axis... >>> >>> EL> In a first time, a bundle can easily provide the full >>> axis/jax-rpc libraries >>> EL> and the web service implementation classes. With a simple >>> HttpContext to >>> EL> retrieve the axis wsdd descriptors, it seems to work... >>> >>> EL> This first solution design is quite poor, since each new >>> webservice should >>> EL> include a full web services stack. I suppose a better >>> design may provide a >>> EL> generic soap/axis bundle, exposing a service for other bundles to >>> EL> deploy/undeploy individual web-services, in a similar style >>> the xml-rpc >>> EL> bundle works. >>> >>> EL> But this seems a bit more complex, and, wisely (?) i though >>> perhaps somebody >>> EL> had already worked on this, and avoid making twice the same things. >>> >>> EL> So, is there anyone in this case ? >>> >>> EL> -- >>> EL> Ephemeris Lappis >>> >>> >>> >>> >>> -- >>> Peter Kriens Mob +33633746480 >>> 9C, Avenue St. Drézéry Tel +33467542167 >>> 34160 Beaulieu, France Tel +15123514821 >>> AOL,Yahoo pkriens ICQ 255570717 >>>
