cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Smyth (JIRA)" <>
Subject [jira] Created: (CXF-275) DestinationFactory and ConduitInitiator not registered for same namespaces
Date Wed, 29 Nov 2006 11:18:21 GMT
DestinationFactory and ConduitInitiator not registered for same namespaces

                 Key: CXF-275
             Project: CXF
          Issue Type: Bug
          Components: Transports
            Reporter: Andrea Smyth

Destination factories are registered for the namespaces:
Conduit Initiators are registered for the namespaces:

As a result, if an endpointtInfo has transportId  ""
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 = "")
public class GreeterImpl implements Greeter {
((org.apache.cxf.jaxws.EndpointImpl)Endpoint.publish(address, new GreeterImpl())).getServer().getEndpoint().getEndpointInfo().getTransportId()
but if the portName is uncommented, the endpointInfo of the published endpoint has transportId
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.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message