Hi Raymond,
I tried that, didn’t seem to be the right place to put it, according to the
WS-Addressing schema and spec...
<wsa:EndpointReference>
<wsa:Address>xs:anyURI</wsa:Address>
<wsa:ReferenceParameters>xs:any*</wsa:ReferenceParameters> ?
<wsa:Metadata>xs:any*</wsa:Metadata>?
</wsa:EndpointReference>
The Action tag is actually on a higher level...
<wsa:To>xs:anyURI</wsa:To> ?
<wsa:From>wsa:EndpointReferenceType</wsa:From> ?
<wsa:ReplyTo>wsa:EndpointReferenceType</wsa:ReplyTo> ?
<wsa:FaultTo>wsa:EndpointReferenceType</wsa:FaultTo> ?
<wsa:Action>xs:anyURI</wsa:Action>
<wsa:MessageID>xs:anyURI</wsa:MessageID> ?
<wsa:RelatesTo RelationshipType="xs:anyURI"?>xs:anyURI</wsa:RelatesTo> *
<wsa:ReferenceParameters>xs:any*</wsa:ReferenceParameters> ?
We noticed that Tuscany was generating all the info it needed for wsa:From in
the ReferenceParameters sub element putting all the tuscany elements there.
Note that /wsa:Action is a required element acording to the spec...
/wsa:To
This OPTIONAL element (whose content is of type xs:anyURI) provides the value
for the [destination] property. If this element is NOT present then the value
of the [destination] property is
"http://www.w3.org/2005/08/addressing/anonymous";.
/wsa:From
This OPTIONAL element (of type wsa:EndpointReferenceType) provides the value
for the [source endpoint] property.
/wsa:ReplyTo
This OPTIONAL element (of type wsa:EndpointReferenceType) provides the value
for the [reply endpoint] property. If this element is NOT present then the
value of the [address] property of the [reply endpoint] EPR is
"http://www.w3.org/2005/08/addressing/anonymous";.
/wsa:FaultTo
This OPTIONAL element (of type wsa:EndpointReferenceType) provides the value
for the [fault endpoint] property.
/wsa:Action
This REQUIRED element (whose content is of type xs:anyURI) conveys the value of
the [action] property.
/wsa:MessageID
This OPTIONAL element (whose content is of type xs:anyURI) conveys the [message
id] property.
/wsa:RelatesTo
This OPTIONAL (repeating) element information item contributes one abstract
[relationship] property value, in the form of an (IRI, IRI) pair. The content
of this element (of type xs:anyURI) conveys the [message id] of the related
message.
/wsa:RelatesTo/@RelationshipType
This OPTIONAL attribute (of type xs:anyURI) conveys the relationship type as an
IRI. When absent, the implied value of this attribute is
"http://www.w3.org/2005/08/addressing/reply";.
/[reference parameters]*
On 3/1/10 2:58 PM, "Raymond Feng" <[email protected]> wrote:
Hi,
The OSOA spec says you can configure binding.ws using:
<binding.ws ..>
<wsa:EndpointReference>...</wsa:EndpointReference>*
</binding.ws>
/binding.ws/wsa:EndpointReference – optional WS-Addressing [6]
EndpointReference that specifies the endpoint for the service or reference.
When this element is present along with the wsdlElement attribute on the parent
element, the wsdlElement attribute value MUST be of the ‘Binding’ form as
specified above, i.e. <WSDL-namespace-URI>#wsdl.binding(<binding-name>).
I haven't personally tried that though.
Thanks,
Raymond
From: Albert Tsang <mailto:[email protected]>
Sent: Monday, March 01, 2010 11:58 AM
To: [email protected]
Subject: ESB and 1.6 integration
Hi,
We’re piloting WSO2 ESB (built around Apache Synapse). We took the
travelsample app and are splitting out the fullapp-bespoketrip composite to run
on a separate JVM instance (machine 2).
The travelcatalog is running separately on another instance (machine 1) and is
making a web service call to a third machine running WSO2 ESB (machine 3).
We’re trying to get WSO2 ESB to proxy the asynch search services running on
machine #2. We had to turn on a flag to preserve the SOAP header and the
additional headers being sent by Tuscany identify the callback. Also had to
turn on WSA support as well to preserve the rest of the From element and the
rest of the reference parameters.
The ESB is expecting the WS Action tag to be set to some value – it appears to
be any value to satisfy the WS-Addressing spec, but Tuscany is not sending it
nor seems to care about it. When we manually inject this tag everything works
fine. I noticed in the WSDL that there is a searchSynch, syncSearchResponse
getPercentComplete and searchAsynch. Looking over the OSOA SCA binding spec
for webservices, it’s not terribly clear where we should add this to the
config...
<reference name="hotelSearch">
<binding.ws
uri="http://machine3.stage.shutterfly.com:8280/services/hotelsearch";>
????
</binding.ws>
<callback>
<binding.ws name="callback"
uri="http://10.2.2.11:8084/Hotel/SearchCallback"/>
</callback>
</reference>
Thanks!
-a-
