You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Dan Diephouse (JIRA)" <ji...@apache.org> on 2006/10/03 21:04:23 UTC
[jira] Commented: (CXF-145) Remove dependency of Soap Binding from
the ReflectionServiceFactory creation
[ http://issues.apache.org/jira/browse/CXF-145?page=comments#action_12439624 ]
Dan Diephouse commented on CXF-145:
-----------------------------------
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.
> Remove dependency of Soap Binding from the ReflectionServiceFactory creation
> ----------------------------------------------------------------------------
>
> Key: CXF-145
> URL: http://issues.apache.org/jira/browse/CXF-145
> Project: CeltiXfire
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.0-M1
> Reporter: Balaji Ravi
> Fix For: 2.0-M1
>
>
> The ReflectionServiceFactoryBean class tries to load all 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?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira