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] Commented: (CXF-3183) http-osgi transport not registered on proper id
Date Fri, 17 Dec 2010 21:42:01 GMT

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

Daniel Kulp commented on CXF-3183:
----------------------------------


I think they are mostly bogus and should be removed.  For example, xformat is a BINDING type,
not a transport.   Likewise for the 2003/05/soap thing.     The soap stuff should be removed
so the soap transport can kick in and do the stuff it needs to do.

> http-osgi transport not registered on proper id
> -----------------------------------------------
>
>                 Key: CXF-3183
>                 URL: https://issues.apache.org/jira/browse/CXF-3183
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.3.0, 2.3.1
>            Reporter: Daniel Kulp
>            Assignee: Daniel Kulp
>             Fix For: 2.3.2
>
>
> The OSGi http transport is not propertly registered on the http://cxf.apache.org/transports/http
transportId.  Thus, the SOAPTransportFactory cannot properly map it and OSGi services fail
to start.
> Workaround is to add a transportId="http://schemas.xmlsoap.org/wsdl/http/" to the jaxws:endpoint
definitions in the spring-dm beans.xml.

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


Mime
View raw message