You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Balaji Ravi (JIRA)" <ji...@apache.org> on 2006/10/03 20:58:19 UTC
[jira] Created: (CXF-145) Remove dependency of Soap Binding from
the ReflectionServiceFactory creation
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
[jira] Updated: (CXF-145) Dynamic discovery of binding creators
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/CXF-145?page=all ]
Dan Diephouse updated CXF-145:
------------------------------
Fix Version/s: 2.0-RC
(was: 2.0-M2)
> Dynamic discovery of binding creators
> -------------------------------------
>
> Key: CXF-145
> URL: http://issues.apache.org/jira/browse/CXF-145
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.0-M1
> Reporter: Balaji Ravi
> Fix For: 2.0-RC
>
>
> It would be nice if in ServerFactoryBean, ServiceImpl, etc, we could dynamically discover which BindingInfoFactoryBean we want to use.
> I am reluctant to have a BindingInfoFactoryBeanFactory as this seems a bit odd. It is nice to be able to just create your own factory bean:
> factory = new SoapBindingInfoFactoryBean()
> factory.setStyle("document");
> ...etc.
> I am not sure what the potential resolution might be. Feel free to add some ideas in the comments.
--
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
[jira] Assigned: (CXF-145) Dynamic discovery of binding creators
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Diephouse reassigned CXF-145:
---------------------------------
Assignee: Dan Diephouse
> Dynamic discovery of binding creators
> -------------------------------------
>
> Key: CXF-145
> URL: https://issues.apache.org/jira/browse/CXF-145
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.0-M1
> Reporter: Balaji Ravi
> Assigned To: Dan Diephouse
> Fix For: 2.0-RC
>
>
> It would be nice if in ServerFactoryBean, ServiceImpl, etc, we could dynamically discover which BindingInfoFactoryBean we want to use.
> I am reluctant to have a BindingInfoFactoryBeanFactory as this seems a bit odd. It is nice to be able to just create your own factory bean:
> factory = new SoapBindingInfoFactoryBean()
> factory.setStyle("document");
> ...etc.
> I am not sure what the potential resolution might be. Feel free to add some ideas in the comments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CXF-145) Remove dependency of Soap Binding from
the ReflectionServiceFactory creation
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ 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
[jira] Closed: (CXF-145) Dynamic discovery of binding creators
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Diephouse closed CXF-145.
-----------------------------
Resolution: Fixed
Dan Kulp just fixed this in SVN.
> Dynamic discovery of binding creators
> -------------------------------------
>
> Key: CXF-145
> URL: https://issues.apache.org/jira/browse/CXF-145
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.0-M1
> Reporter: Balaji Ravi
> Assigned To: Dan Diephouse
> Fix For: 2.0-RC
>
>
> It would be nice if in ServerFactoryBean, ServiceImpl, etc, we could dynamically discover which BindingInfoFactoryBean we want to use.
> I am reluctant to have a BindingInfoFactoryBeanFactory as this seems a bit odd. It is nice to be able to just create your own factory bean:
> factory = new SoapBindingInfoFactoryBean()
> factory.setStyle("document");
> ...etc.
> I am not sure what the potential resolution might be. Feel free to add some ideas in the comments.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-145) Dynamic discovery of binding creators
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/CXF-145?page=all ]
Dan Diephouse updated CXF-145:
------------------------------
Summary: Dynamic discovery of binding creators (was: Remove dependency of Soap Binding from the ReflectionServiceFactory creation)
Fix Version/s: 2.0-M2
(was: 2.0-M1)
Description:
It would be nice if in ServerFactoryBean, ServiceImpl, etc, we could dynamically discover which BindingInfoFactoryBean we want to use.
I am reluctant to have a BindingInfoFactoryBeanFactory as this seems a bit odd. It is nice to be able to just create your own factory bean:
factory = new SoapBindingInfoFactoryBean()
factory.setStyle("document");
...etc.
I am not sure what the potential resolution might be. Feel free to add some ideas in the comments.
was:
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?
I've updated the issue to more accurately describe the issue at hand and schedule for M2.
> Dynamic discovery of binding creators
> -------------------------------------
>
> Key: CXF-145
> URL: http://issues.apache.org/jira/browse/CXF-145
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.0-M1
> Reporter: Balaji Ravi
> Fix For: 2.0-M2
>
>
> It would be nice if in ServerFactoryBean, ServiceImpl, etc, we could dynamically discover which BindingInfoFactoryBean we want to use.
> I am reluctant to have a BindingInfoFactoryBeanFactory as this seems a bit odd. It is nice to be able to just create your own factory bean:
> factory = new SoapBindingInfoFactoryBean()
> factory.setStyle("document");
> ...etc.
> I am not sure what the potential resolution might be. Feel free to add some ideas in the comments.
--
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