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 2010/12/10 18:35:01 UTC
[jira] Created: (CXF-3183) http-osgi transport not registered on
proper id
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.1, 2.3.0
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.
[jira] Commented: (CXF-3183) http-osgi transport not registered on
proper id
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972570#action_12972570 ]
Christian Schneider commented on CXF-3183:
------------------------------------------
I just noticed that in http-jetty there is an id http://schemas.xmlsoap.org/wsdl/http/ and http://schemas.xmlsoap.org/wsdl/http present. Can this be the problem?
> 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.
[jira] Commented: (CXF-3183) http-osgi transport not registered on
proper id
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972655#action_12972655 ]
Christian Schneider commented on CXF-3183:
------------------------------------------
Do you have any idea why the cxf-extension-http-jetty.xml only contains four transport ids
<value>http://cxf.apache.org/transports/http</value>
<value>http://cxf.apache.org/transports/http/configuration</value>
<value>http://schemas.xmlsoap.org/wsdl/http</value>
<value>http://schemas.xmlsoap.org/wsdl/http/</value>
while cxf-extension-http-osgi.xml contains seven lines if I add the missing id.
<value>http://cxf.apache.org/bindings/xformat</value>
<value>http://schemas.xmlsoap.org/soap/http</value>
<value>http://schemas.xmlsoap.org/wsdl/http/</value>
<value>http://schemas.xmlsoap.org/wsdl/soap/http</value>
<value>http://www.w3.org/2003/05/soap/bindings/HTTP/</value>
<value>http://cxf.apache.org/transports/http</value>
<value>http://cxf.apache.org/transports/http/configuration</value>
Btw. I have added the id to the cxf-extension-http-osgi.xml file on trunk.
> 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.
[jira] Commented: (CXF-3183) http-osgi transport not registered on
proper id
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CXF-3183) http-osgi transport not registered on
proper id
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972576#action_12972576 ]
Daniel Kulp commented on CXF-3183:
----------------------------------
On trunk, rt/transports/http-osgi/src/main/resources/META-INF/cxf/osgi/cxf-extension-osgi.xml contains:
{code}
<value>http://cxf.apache.org/bindings/xformat</value>
<value>http://schemas.xmlsoap.org/soap/http</value>
<value>http://schemas.xmlsoap.org/wsdl/http/</value>
<value>http://schemas.xmlsoap.org/wsdl/soap/http</value>
<value>http://www.w3.org/2003/05/soap/bindings/HTTP/</value>
<value>http://cxf.apache.org/transports/http/configuration</value>
{code}
which doesn't have the http://cxf.apache.org/transports/http id. The above list should exactly match what is in:
rt/transports/http-jetty/src/main/resources/META-INF/cxf/cxf-extension-http-jetty.xml
Someone really just needs to copy it and test it.
> 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.
[jira] Resolved: (CXF-3183) http-osgi transport not registered on
proper id
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-3183.
------------------------------
Resolution: Fixed
Freeman already fixed this.
> 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.
[jira] Commented: (CXF-3183) http-osgi transport not registered on
proper id
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972568#action_12972568 ]
Christian Schneider commented on CXF-3183:
------------------------------------------
The transport id is present in the cxf-extension-osgi.xml config file in cxf-transports-http-osgi. Do you know where it is missing?
> 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.