geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Blevins <>
Subject Re: mutiple WebServiceBuilder gbeans
Date Thu, 16 Feb 2006 21:33:38 GMT
On Feb 16, 2006, at 7:50 AM, David Jencks wrote:

> sorry for the delay in replying
> On Feb 10, 2006, at 9:46 AM, Conrad O'Dea wrote:
>> Hi David,
>> On 10 Feb 2006, at 16:04, David Jencks wrote:
>>>> in the current default configuration for Geronimo, there appears  
>>>> to be single WebServiceBuilder deployed which is the  
>>>> AxisBuilder.  Is it possible to have a second builder of this  
>>>> type deployed? Is so what will happen when another Gbean (for  
>>>> example the Jetty or Tomcat deployer) invokes on it?
>>>> Basically, I am looking for a way to deploy another  
>>>> WebServiceBuilder that can be used by the module deployers  
>>>> without having to update the plans for each, if possible.
>>> You won't be able to use it for ejb web services because the  
>>> openejb web service implementation is hard coded to use axis.
>> Is there any reason that the OpenEJB stuff must use Axis or could  
>> it be updated to be more flexible?
> I don't think there is any fundamental reason but right now it is  
> coded that way and in the limited time I've been able to look at it  
> I haven't seen how to disentangle it.   David Blevins might have a  
> better idea how to approach this.

The webservices support in OpenEJB and Geronimo both use this  
interface that I came up with: 

That can be wrapped in a servlet, wrapped directly by jetty, or  
wrapped in anything that can support an http-like request/response.   
These wrapping things I'm talking about are essentially front-ends  
and all our front-ends rely upon that interface cleanly and are not  
tied to any WebServiceContainer we have.

The Axis implementation is here: 

An out-of-date XFire implementation is here: 

I prototyped on XFire first and then eventually created an Axis  
implementation which is what we certify with.  The runtime is very  
decoupled and can essentially support any webservice that implements  
the WebServiceContainer interface.

It's pretty much deployment that ties us to Axis.  If you can find  
what we need to do to peal our Axis implementation out, I'm happy to  

I'd like to see XFire as an option again, myself.


View raw message