Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Java-SCA-1.2
-
None
-
Patch Available
Description
Web Service Binding Specification v1.00 - Sec 2.1.1 - Lines 70 to 85:
70 2.1.1 Endpoint URI resolution
71 The rules for resolving the URI at which an SCA service is hosted, or SCA reference targets,
72 when used with binding.ws (in precedence order) are:
73 1. The URIs in the endpoint(s) of the referenced WSDL
74 or
75 The URI specified by the wsa:Address element of the wsa:EndpointReference,
76 2. The explicitly stated URI in the "uri" attribute of the binding.ws element, which may be
77 relative,
78 3. The implicit URI as defined by the Assembly specification
79 The URI in the WSDL endpoint or in the wsa:Address of an EPR may be a relative URI, in which
80 case it is relative to the URI defined in (2) or (3). The wsa:Address element can be the empty
81 relative URI, in which case it uses the URI defined in (2) or (3) directly. This allows the EPR
82 writer to specify reference parameters, metadata and other EPR contents while allowing the URI
83 to be chosen by the deployer.
----------
I am using a URI "http://localhost:8080/AService" on binding.ws element. With this in place,
Issue 1: When I use an empty wsa:Address element, the Endpoint URI resolved should be "http://localhost:8080/AService" whereas it is resolved to "http://localhost:8080/".
Issue 2: When I use a relative uri of "inAddress" in wsa:Address element, the Endpoint URI resolved should be "http://localhost:8080/AService/inAddress" whereas it is resolved to "http://localhost:8080/inAddress".
The bottom line is that the Endpoint URI resolution is not correct when relative URI's is used in wsa:Address of an EPR.
Attachments
Attachments
Issue Links
- is depended upon by
-
-
- Closed
-