[jbossws-issues] [JBoss JIRA] Commented: (JBWS-1844) The current spi Provider API does not implement instantiation of class W3CEndpointReference via method createW3CEndpointReference.

[Andrew Dinn (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBWS-1844?page=comments#action_12398514 ] 
            
Andrew Dinn commented on JBWS-1844:
-----------------------------------

I would like to clarify the requirements of the current prototype implementation of Web Services Transactions based on JaxWS (these have been clarified in trials using the Glassfish WS stack).

The prototype creates endpoints using the W3CEndpointReferenceBuilder API

  public W3CEndpointReference build()

In all cases the endpoints are created by a service co-located (in the same web server) as the target service whose name is supplied to the builder class. Before calling build() the caller supplies a service name, a port (endpoint) name, an endpoint address and reference parameters  using the following W3CEndpointReferenceBuilder APIs. 

  public W3CEndpointReferenceBuilder address(String address)
  public W3CEndpointReferenceBuilder serviceName(QName serviceName)
  public W3CEndpointReferenceBuilder endpointName(QName endpointName)
  public W3CEndpointReferenceBuilder referenceParameter(Element referenceParameter)

The caller does not currently provide WSDL or metadata i.e. it does not depend on the implementation of APIs

  public W3CEndpointReferenceBuilder wsdlDocumentLocation(String wsdlDocumentLocation)
  public W3CEndpointReferenceBuilder metadata(Element metadataElement)

On receipt of an endpoint clients create an instance of Service, supplying their own copy of the service WSDL. They then employ the Service API

  public <T> T getPort(EndpointReference endpointReference,
           Class<T> serviceEndpointInterface, WebServiceFeature... features)

to obtain a port enabling invocation of the remote service. It is assumed that the address in the endpoint is used to locate the service and that the reference parameters stored in the endpoint are inserted into outgoing messages.


> The current spi Provider API does not implement instantiation of class W3CEndpointReference via method createW3CEndpointReference.
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBWS-1844
>                 URL: http://jira.jboss.com/jira/browse/JBWS-1844
>             Project: JBoss Web Services
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>    Affects Versions: jbossws-2.0.1
>            Reporter: Andrew Dinn
>            Priority: Critical
>             Fix For: jbossws-native-2.0.4
>
>
> The current spi Provider API does not implement instantiation of class W3CEndpointReference via method createW3CEndpointReference. This underpins availability of W3CEndpointRefrence via the related APIs in Endpoint, W3CEndpointReferenceBuilder and WebServiceContext. Implementation of transaction support for web services using JBossWS native stack requires the ability to instantiate W3CEndpointReference using W3CEndpointReferenceBuilder.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira