cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Diephouse <>
Subject Re: Soap Binding dependency during service model creation
Date Tue, 03 Oct 2006 19:18:57 GMT
Hi Balaj,
Didn't realize you posted this to the list too. Here's what I said in 
the JIRA issue: We do this because the frontend has specific knowledge 
of how to create the bindings. For instance, JAX-WS has specific 
information about SOAP. Hence we need to have a dependency on the SOAP 
binding. I am in the midst of some cleanup on this and clarifying how 
frontends work right now. I am just trying to get my tests to pass. 
Hopefully I can get the commit in yet today and you can take a look.

We could maybe include a more dynamic method to do this - i.e. load 
default bindings only if the exist, definitely something good to think 

- Dan

Balaji Ravi wrote:
> Hi,
> There is a dependency on the soap binding jar in the runtime when i am 
> not
> using the soap binding in my wsdl.
> The ReflectionServiceFactoryBean class tries to load the Soap Binding
> specific classes thereby creating a dependency of loading the soap 
> binding
> jar when not needed...
> We should remove it from that class & let the soap binding load it 
> up... If
> i just want to use xml binding, why should i load up the soap binding 
> jar?
> JIRA: 
> **<>

> Thanks
> Balaji

Dan Diephouse
Envoi Solutions

View raw message