Eclipse Community Forums: Equinox

Help

Home

Home » Eclipse Projects » Equinox » Axis2 in Equinox

Show: Today's Messages :: Show Polls :: Message Navigator

Axis2 in Equinox [message #91441]

Sun, 01 July 2007 17:55

Messages: 9
Registered: July 2009

Junior Member

Hi,

I really want to add Web Service support to my run-time stack, preferably
with the Jetty server
Axis2 seams like the choice and I saw that Apache Muse has some OSGi bundle
for Axis2. But I really need
some advice to get going

BR

Lars

Report message to a moderator

Re: Axis2 in Equinox [message #91634 is a reply to message #91441]

Fri, 06 July 2007 06:55

Karsten Panier

Messages: 57
Registered: July 2009

Member

Lars schrieb:
> Hi,
>
> I really want to add Web Service support to my run-time stack, preferably
> with the Jetty server
> Axis2 seams like the choice and I saw that Apache Muse has some OSGi bundle
> for Axis2. But I really need
> some advice to get going
>
> BR
>
> Lars
>
>
>
Hi,
I am interested in this topic too. I read this tutorial:
http://www-128.ibm.com/developerworks/edu/ws-dw-ws-eclipsepl ugin.html
Now I can run webservices with axis 1.4 in tomcat with osgi and in
equinox with jetty. The disadvantage is that I have one central config
file "server-config.wsdd" to register the webservices. Another Point is
that I want to use axis2 and not axis.
I looked at the corona and ohf projects. They seems to use axis2 for
their webservices. I didn't find docs or any simple code example to
understand how that works.
Where can I find some Examples about it?
regards
karsten

Report message to a moderator

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

Report message to a moderator

Re: Axis2 in Equinox [message #91902 is a reply to message #91870]

Tue, 10 July 2007 15:17

Karsten Panier

Messages: 57
Registered: July 2009

Member

Jörg Lehmann schrieb:
> 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
Hi Jörg,
how managed you to get Axis2 running in equinox? I packed the necessory
jars in one bundle. Than i registered the AxisServelt as a
org.osgi.service.http.HttpService.
I am not sure if this is the right way. I also don't know how to deploy
a webservice to it.
Any hints?
Thanks
Karsten

Report message to a moderator

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

Report message to a moderator