|
|
Re: Axis2 in Equinox [message #91870 is a reply to message #91441] |
Tue, 10 July 2007 10:38 |
Eclipse User |
|
|
|
Originally posted by: the.dev.ich-will-net.de
Hi,
We managed to get Axis2 running within the Jetty http service(based on Eclipse 3.2.2) for some simple prototyping. So there might be some stuff to do, but it is working in principle. So, what do you want to know?
Jörg
|
|
|
|
Re: Axis2 in Equinox [message #91991 is a reply to message #91902] |
Wed, 11 July 2007 17:52 |
Eclipse User |
|
|
|
Originally posted by: the.dev.ich-will-net.de
Hi Karsten,
I kind of remember that OHF also used osgi services to register their web services. But i think that you'll probably have to dig much more deeper into the Axis2 framework to configure & provide web services that way.
We went a little different way for our prototype. We simply used the Jetty Http Implementation and registered the AxisServlet and all other aliases (see Axis2' web.xml). Instead of stuffing all libraries into one bundle, we separated them into logical packages like axis libs, several commons libs, ...
We've got one bundle which acts as some kind of Axis2-OSGi-Wrapper which has a WebContent subfolder (with a similar stucture like the axis2 web-app), which registers the servlets and http context to the http service implementation. By putting your webservice archives to the according services folder you can make the services available to clients.
If you once got it going you can continue with more sophisticated logic: Our next step was to provide the custom webservices on a component base. I.e. we provided an extension point for custom bundles (within the wrapper bundle) to add more services by giving their *.wsdd and service.xml file. The wrapper bundle collects all bundles on start-up and generates the according aar files in it's service folder (only the configuration files are included, the implementation still resides in the original bundles and is accessible via buddy class-loading). The next step would have been to avoid the creation of the 'dummy' aar files and add / configure the services directly in code, but with stop at that point for now. If that one is done it is probably no big step to use a osgi service instead of the indirection via jetty.
A very pragmatic solution, but it helped us to get started.
Hope it helps you a just little bit..
Jörg
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04606 seconds