cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-859) Provider could support more message types
Date Fri, 09 Sep 2011 17:55:10 GMT

     [ https://issues.apache.org/jira/browse/CXF-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Kulp resolved CXF-859.
-----------------------------

       Resolution: Won't Fix
    Fix Version/s: Invalid


This improvement request has been open for years and no-one has stepped up to implement it.
 As such, it does not seems to be a priority for the existing CXF community.   If, in the
future, someone would like to tackle this, feel free to open is and attach a patch.

> Provider could support more message types
> -----------------------------------------
>
>                 Key: CXF-859
>                 URL: https://issues.apache.org/jira/browse/CXF-859
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-WS Runtime
>            Reporter: Michal Safr
>             Fix For: Invalid
>
>
> Provider could support raw CXF message types. Daniel Kulp asked me to create this issue.
You can find more information at http://www.nabble.com/YOKO---CXF-CORBA-Web-Service-using-Provider%3CCorbaMessage%3E-tf4157811.html.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message