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/10/03 18:39:23 UTC
[jira] Resolved: (CXF-275) DestinationFactory and ConduitInitiator
not registered for same namespaces
[ https://issues.apache.org/jira/browse/CXF-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-275.
-----------------------------
Resolution: Fixed
This was fixed a long time ago
> DestinationFactory and ConduitInitiator not registered for same namespaces
> --------------------------------------------------------------------------
>
> Key: CXF-275
> URL: https://issues.apache.org/jira/browse/CXF-275
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Reporter: Andrea Smyth
>
> Destination factories are registered for the namespaces:
> http://cxf.apache.org/transports/jms/configuration
> http://schemas.xmlsoap.org/wsdl/soap/http
> http://schemas.xmlsoap.org/wsdl/soap12/
> http://cxf.apache.org/transports/local
> http://schemas.xmlsoap.org/wsdl/http/
> http://cxf.apache.org/transports/jms
> http://cxf.apache.org/bindings/xformat
> http://schemas.xmlsoap.org/soap/
> http://cxf.apache.org/transports/http/configuration
> http://schemas.xmlsoap.org/wsdl/soap/
> http://schemas.xmlsoap.org/soap/http
> http://www.w3.org/2003/05/soap/bindings/HTTP/
> Conduit Initiators are registered for the namespaces:
> http://cxf.apache.org/transports/jms/configuration
> http://schemas.xmlsoap.org/wsdl/soap/http
> http://cxf.apache.org/transports/local
> http://schemas.xmlsoap.org/wsdl/http/
> http://cxf.apache.org/transports/jms
> http://cxf.apache.org/bindings/xformat
> http://cxf.apache.org/transports/http/configuration
> http://schemas.xmlsoap.org/soap/http
> http://www.w3.org/2003/05/soap/bindings/HTTP/
> As a result, if an endpointtInfo has transportId "http://schemas.xmlsoap.org/wsdl/soap/" a destination can be created for it but no conduit. This is confusing, and there is no good reason (such as: a particular transport is only supported on the client side).
> Moreover it is not clear at all why and how different ways of annotating a JAX-WS implementor result in different transportIds for that endpoint:
> For the following implementor:
> @javax.jws.WebService(serviceName = "GreeterService",
> // portName = "GreeterPort",
> endpointInterface = "org.apache.cxf.hello_world_soap_http.Greeter",
> targetNamespace = "http://cxf.apache.org/hello_world_soap_http")
>
> public class GreeterImpl implements Greeter {
> ...
> }
> ((org.apache.cxf.jaxws.EndpointImpl)Endpoint.publish(address, new GreeterImpl())).getServer().getEndpoint().getEndpointInfo().getTransportId() returns http://schemas.xmlsoap.org/wsdl/soap/
> but if the portName is uncommented, the endpointInfo of the published endpoint has transportId http://schemas.xmlsoap.org/soap/http.
> Very frustrating in the case of RM, where for a published application server endpoint we take its endpoint Info's transport Id to obtain a conduit - in order to support server seide originated standalone RM protocol messages such as SequenceAcknowledgments!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.