You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2009/07/06 22:17:14 UTC

[jira] Commented: (CXF-2264) WSDL extension for WSDL usage

    [ https://issues.apache.org/jira/browse/CXF-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727756#action_12727756 ] 

Daniel Kulp commented on CXF-2264:
----------------------------------


I just committed a different "version" of this (but used your test case) that cleans up some other transportId handling issues throughout the code but also keeps the "soap" stuff in the soap binding.   That will hopefully resolve some of this as well as a bunch of other issues I've seen.

> WSDL extension for WSDL usage
> -----------------------------
>
>                 Key: CXF-2264
>                 URL: https://issues.apache.org/jira/browse/CXF-2264
>             Project: CXF
>          Issue Type: Sub-task
>            Reporter: Liu Cong
>            Assignee: Willem Jiang
>             Fix For: 2.2.3
>
>         Attachments: wsdl-patch.patch, wsdl-patch.txt, wsdl-patch2.txt
>
>
> Make the WSDL definition conformance with the SOAP/JMS specification. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.