You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2010/01/09 11:15:54 UTC
[jira] Created: (CXF-2611) Remove code to set wsdllocation in copy
of binding.xml
Remove code to set wsdllocation in copy of binding.xml
------------------------------------------------------
Key: CXF-2611
URL: https://issues.apache.org/jira/browse/CXF-2611
Project: CXF
Issue Type: Improvement
Components: Tooling
Reporter: Christian Schneider
Assignee: Christian Schneider
Fix For: 2.3
I recently added code to add the wsdlLocation of the wsdl currently processed to the binding file if the wsdlLocation was empty. Dan point out that the codegen already acts this way (see mail below). So I will remove this code again and document how to use it.
-----
In your case, wherever we match the jaxws binding file up to a wsdl, if
wsdlLocation is null and that option is set, instead of throwing an exception,
assume that it's the current wsdl location.
Actually, looking at the code in CustomizationParser.java, line 491, that's
exactly what we DO do. Thus, I'm wondering if you really needed to do
anything at all. We're probably not spec compliant in this regards right
now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2611) Remove code to set wsdllocation in copy
of binding.xml
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider resolved CXF-2611.
--------------------------------------
Resolution: Fixed
> Remove code to set wsdllocation in copy of binding.xml
> ------------------------------------------------------
>
> Key: CXF-2611
> URL: https://issues.apache.org/jira/browse/CXF-2611
> Project: CXF
> Issue Type: Improvement
> Components: Tooling
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 2.3
>
>
> I recently added code to add the wsdlLocation of the wsdl currently processed to the binding file if the wsdlLocation was empty. Dan point out that the codegen already acts this way (see mail below). So I will remove this code again and document how to use it.
> -----
> In your case, wherever we match the jaxws binding file up to a wsdl, if
> wsdlLocation is null and that option is set, instead of throwing an exception,
> assume that it's the current wsdl location.
> Actually, looking at the code in CustomizationParser.java, line 491, that's
> exactly what we DO do. Thus, I'm wondering if you really needed to do
> anything at all. We're probably not spec compliant in this regards right
> now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2611) Remove code to set wsdllocation in copy
of binding.xml
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-2611:
-----------------------------
Fix Version/s: (was: 2.3)
2.2.6
> Remove code to set wsdllocation in copy of binding.xml
> ------------------------------------------------------
>
> Key: CXF-2611
> URL: https://issues.apache.org/jira/browse/CXF-2611
> Project: CXF
> Issue Type: Improvement
> Components: Tooling
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 2.2.6
>
>
> I recently added code to add the wsdlLocation of the wsdl currently processed to the binding file if the wsdlLocation was empty. Dan point out that the codegen already acts this way (see mail below). So I will remove this code again and document how to use it.
> -----
> In your case, wherever we match the jaxws binding file up to a wsdl, if
> wsdlLocation is null and that option is set, instead of throwing an exception,
> assume that it's the current wsdl location.
> Actually, looking at the code in CustomizationParser.java, line 491, that's
> exactly what we DO do. Thus, I'm wondering if you really needed to do
> anything at all. We're probably not spec compliant in this regards right
> now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CXF-2611) Remove code to set wsdllocation in copy
of binding.xml
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider closed CXF-2611.
------------------------------------
> Remove code to set wsdllocation in copy of binding.xml
> ------------------------------------------------------
>
> Key: CXF-2611
> URL: https://issues.apache.org/jira/browse/CXF-2611
> Project: CXF
> Issue Type: Improvement
> Components: Tooling
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 2.3
>
>
> I recently added code to add the wsdlLocation of the wsdl currently processed to the binding file if the wsdlLocation was empty. Dan point out that the codegen already acts this way (see mail below). So I will remove this code again and document how to use it.
> -----
> In your case, wherever we match the jaxws binding file up to a wsdl, if
> wsdlLocation is null and that option is set, instead of throwing an exception,
> assume that it's the current wsdl location.
> Actually, looking at the code in CustomizationParser.java, line 491, that's
> exactly what we DO do. Thus, I'm wondering if you really needed to do
> anything at all. We're probably not spec compliant in this regards right
> now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.