ESB and 1.6 integrationHi,

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 
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- 

Reply via email to