Thank you for fast respond. I will look at the mentioned components.
But I will be much appreciated for any samples or links regarding real usage
of such components in ESB. 



Gert Vanthienen wrote:
> 
> L.S.,
> 
> 
> ServiceMix itself doesn't have a plain TCP/IP binding component, but you 
> can use servicemix-camel to deploy a Camel route that uses the Camel 
> MINA component (http://activemq.apache.org/camel/mina.html) to handle 
> this.  For invoking the webservice, you can use the servicemix-http 
> component.  IIRC, servicemix-camel uses synchronous communication to 
> interact with other services on the ESB by default, so you shouldn't 
> have to a lot there.
> 
> 
> Does this help?
> 
> Gert
> 
> 
> Pavlo Fenoga wrote:
>> Hello,
>> I am evaluating ServiceMix 3.2.1 to be used as ESB solution for
>> integrating
>> different healthcare applications.
>> I have spent some time to play with provided examples and as for now
>> everything looks very promising.
>> Now I try to implement simple real scenario.
>> Application A should communicate with Application B
>> Appl. A uses TCP/IP protocol to send requests in XML format and receive
>> responds in XML format as well.
>> Each request is a XML message with prefix and suffix.
>> Request from appl. A should be translated to SOAP message in order to
>> invoke
>> WebService of  Appl. B
>> Appl. B should respond on request sending XML message back to appl. A 
>> So, communication is synchronous and looks like the following:
>> TCP <-> XSLT <-> WS
>>
>> The questions are:
>> 1.   What BC should be used for working with TCP protocol?
>> 2.   What BC should be used to invoke WebService?
>> 3.   How to make communication synchronous? All provided examples seem to
>> be
>> asynchronous.
>>
>> Thank you.
>>
>>   
> 
> 
> 
> -----
> ---
> Gert Vanthienen
> http://www.anova.be
> 

-- 
View this message in context: 
http://www.nabble.com/ServiceMix-evaluation-for--TCP-%3C-%3E-XSLT-%3C-%3E-WS-tp15329736s12049p15331578.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to