Hi Dimuthu,

In general, if you want to convert a message that comes to ESB, to the
format of back-end service, you could use PayloadFactory mediator [1]. But,
if it's a simple transformation like your example, you could simply use a
XSLT transformation [2].

Hope this helps.

[1] http://docs.wso2.org/display/ESB470/PayloadFactory+Mediator

[2] http://docs.wso2.org/display/ESB470/XSLT+Mediator


On Sun, Dec 1, 2013 at 9:21 AM, Dimuthu Upeksha <[email protected]> wrote:

> Hi all,
> Let's say I want to change a message came from a client to a service using
> ESB. As an example the soap message came from client to the ESB is
>
> <?xml version="1.0" encoding="UTF-8"?>
> <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/";>
> <s:Body>
>  <tns:getCustomerName xmlns:tns="
> http://axiom.service.quickstart.samples/xsd";>
>  <tns:name>0</tns:name>
>  </tns:getCustomerName>
> </s:Body>
> </s:Envelope>
>
> It says to get the customer bounded to the order 0. If the service starts
> orders from index 1,2.... (1 base) ESB needs to increment 0 by 1. How can I
> do it? I couldn't find a way to do it. I think it should be done through
> sequences. But I don't know a way to do it.
>
>
>
>
> On Sat, Nov 30, 2013 at 8:44 PM, Dimuthu Upeksha <[email protected]>wrote:
>
>> Hi Nirmal, Udana
>> Thank you for the clarification. It helped me a lot. I thought 50239 is
>> a client's port. My bad.
>>
>> Thank you
>> Dimuthu
>>
>>
>> On Sat, Nov 30, 2013 at 7:58 PM, Isuru Udana <[email protected]> wrote:
>>
>>> Hi Dimuthu,
>>>
>>> Client -> ESB -> Axis2 Server
>>>
>>> In the above scenario ESB is acting as a server as well as a client.
>>>
>>> 1. Client -> ESB (ESB Acting as a server)
>>> 2. ESB -> Axis2 Server (ESB Acting as a client)
>>>
>>> So 50239 might be the be the Ephemeral port of ESB when it is
>>> communicating with axis2 server.
>>>
>>>
>>>
>>> On Sat, Nov 30, 2013 at 7:34 PM, Dimuthu Upeksha <[email protected]>wrote:
>>>
>>>>  Hi all,
>>>>
>>>> I'm an intern of WSO2. I am going through several tutorials about WSO2
>>>> ESB and managed to test some samples given in  [1]. As given in the
>>>> tutorial I was able to simulate message mediating done in ESB. Then I
>>>> captured the packets that are transferred through localhost using Wireshark
>>>> [2]. I could see three ports involved in the process.
>>>> Port 9000 : Listener port of Axis 2 server
>>>> Port 8280 : Port of ESB (I think so)
>>>> Port 50238 : Port of the client
>>>> Port 50239 : I have no idea about this port however it seems like
>>>> another port of the client
>>>>
>>>> At the first set of packets I could see that client is communicating
>>>> with the ESB and ESB is communicating with the Axis2 server : which is
>>>> legal. But at the end I could see that Port 50239 is communicating directly
>>>> with 9000 (Packet no 11). Is this legal? Shouldn't it communicate with port
>>>> 8280? If client communicate with the server directly what is the role of
>>>> ESB as a message mediator? Correct me if I'm wrong.
>>>>
>>>> Thank you
>>>>
>>>> Best Regards
>>>>
>>>> [1]
>>>> http://docs.wso2.org/display/ESB470/Lesson+Two%3A+Mediating+Messages
>>>> [2] https://www.dropbox.com/s/skxozdvu61kyd0c/packet_capture
>>>>
>>>> Dimuthu Upeksha
>>>>
>>>> _______________________________________________
>>>> Dev mailing list
>>>> [email protected]
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *Isuru Udana*
>>>  Senior
>>> * Software Engineer*
>>> WSO2 Inc.; http://wso2.com
>>> email: [email protected] cell: +94 77 3791887
>>> blog: http://mytecheye.blogspot.com/
>>> twitter: http://twitter.com/isudana
>>>
>>
>>
>


-- 

Thanks & regards,
Nirmal

Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to