[prev in list] [next in list] [prev in thread] [next in thread]
List: wsf-java-user
Subject: Re: [User] Create WSO2 ESB Customized Transport
From: Lucky Haryadi <xzorax89 () gmail ! com>
Date: 2012-09-17 9:47:41
Message-ID: CABGr5cZKyRQOecGO4FXPFiAiwwiOQOkPzxTXUo8Frq_an4sV1g () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Thanks, Paul.
Yes, maybe the simplest thing to do is create a custom JPOS mediator. But
my requirement is to create custom transport layer, while the mediators are
used for business logic.
I think I got a clue for what I want to do. As described in the
documentation, to enable TCP Transport, just add several lines to
axis2.xml. It describes that the TCP Receiver module loads a class called
org.apache.axis2.transport.tcp.TCPTransportListener. Then, I discovered
that WSO2 load the TCPTransportListener from a library called
axis2-1.6.1.wso2v4.jar on directory repository/components/plugins.
Where I can get source code of axis2-1.6.1.wso2v4.jar, so I can add other
customized transport layer, for example
org.apache.axis2.transport.tcp.ISOTransportListener and add it to axis2.xml?
On Mon, Sep 17, 2012 at 4:19 PM, Paul Fremantle <paul@wso2.com> wrote:
> Lucky
>
> I'm not an expert on the TCP transport, but I think what you want to do is
> use your JPOS code as a mediator and the TCP transport together. Once the
> message comes in on the TCP transport you can access it as binary byte[]
> via the PayloadHelper interface.
>
> Paul
>
>
> On 17 September 2012 06:38, Lucky Haryadi <xzorax89@gmail.com> wrote:
>
>> Thanks, Paul.
>> Actually I've already developed a module utilizing JPOS so it is easily
>> configurable by xml configuration. I still have no idea how to integrate it
>> with WSO2 ESB. Is it possible to create a new customized TCP Transport
>> Module and attach it to WSO2 ESB? If yes, please give me any guidance to
>> write the customized transport modules :-)
>>
>> On Mon, Sep 17, 2012 at 12:28 PM, Paul Fremantle <paul@wso2.com> wrote:
>>
>>> Lucky
>>>
>>> You might well be able to use the TCP transport together with an ISO
>>> 8583 library like this to parse the messages:
>>> https://github.com/vikrantlabde/iso8583-Java
>>>
>>> If not there are people who will help you figure out how to write a
>>> transport here :-)
>>>
>>> Paul
>>>
>>> On 17 September 2012 06:08, Lucky Haryadi <xzorax89@gmail.com> wrote:
>>>
>>>> I want to create a new transport processor on WSO2 ESB. This transport
>>>> is to provide ISO 8583 message processing and transform Raw TCP to SOAP
>>>> message, vice versa. On the source code, there is a transport management
>>>> object and inherited by several transport service class such as JMS, HTTP,
>>>> HTTPS, etc. I have several questions:
>>>>
>>>> 1. How the transport management object works?
>>>> 2. Is that possible to recode TCP service source code and redeploy
>>>> with my customized actions?
>>>>
>>>> Thanks.
>>>>
>>>> _______________________________________________
>>>> User mailing list
>>>> User@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/user
>>>>
>>>>
>>>
>>>
>>> --
>>> Paul Fremantle
>>> CTO and Co-Founder, WSO2
>>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>>
>>> UK: +44 207 096 0336
>>> US: +1 646 595 7614
>>>
>>> blog: http://pzf.fremantle.org
>>> twitter.com/pzfreo
>>> paul@wso2.com
>>>
>>> wso2.com Lean Enterprise Middleware
>>>
>>> Disclaimer: This communication may contain privileged or other
>>> confidential information and is intended exclusively for the addressee/s.
>>> If you are not the intended recipient/s, or believe that you may have
>>> received this communication in error, please reply to the sender indicating
>>> that fact and delete the copy you received and in addition, you should not
>>> print, copy, retransmit, disseminate, or otherwise use the information
>>> contained in this communication. Internet communications cannot be
>>> guaranteed to be timely, secure, error or virus-free. The sender does not
>>> accept liability for any errors or omissions.
>>>
>>>
>>
>
>
> --
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>
> UK: +44 207 096 0336
> US: +1 646 595 7614
>
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> paul@wso2.com
>
> wso2.com Lean Enterprise Middleware
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, retransmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
>
[Attachment #5 (text/html)]
Thanks, Paul.<div><br></div><div>Yes, maybe the simplest thing to do is create a \
custom JPOS mediator. But my requirement is to create custom transport layer, while \
the mediators are used for business logic.</div><div><br> </div><div>I think I got a \
clue for what I want to do. As described in the documentation, to enable TCP \
Transport, just add several lines to axis2.xml. It describes that the TCP Receiver \
module loads a class called org.apache.axis2.transport.tcp.TCPTransportListener. \
Then, I discovered that WSO2 load the TCPTransportListener from a library called \
axis2-1.6.1.wso2v4.jar on directory repository/components/plugins. </div> \
<div><br></div><div>Where I can get source code of axis2-1.6.1.wso2v4.jar, so I can \
add other customized transport layer, for example \
org.apache.axis2.transport.tcp.ISOTransportListener and add it to \
axis2.xml?</div><div> <br><div class="gmail_quote">On Mon, Sep 17, 2012 at 4:19 PM, \
Paul Fremantle <span dir="ltr"><<a href="mailto:paul@wso2.com" \
target="_blank">paul@wso2.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> Lucky<div><br></div><div>I'm not an expert on the TCP \
transport, but I think what you want to do is use your JPOS code as a mediator and \
the TCP transport together. Once the message comes in on the TCP transport you can \
access it as binary byte[] via the PayloadHelper interface.</div> <span \
class="HOEnZb"><font color="#888888">
</font></span><div><span class="HOEnZb"><font \
color="#888888"><br>Paul</font></span><div><div class="h5"><br><br><div \
class="gmail_quote">On 17 September 2012 06:38, Lucky Haryadi <span dir="ltr"><<a \
href="mailto:xzorax89@gmail.com" target="_blank">xzorax89@gmail.com</a>></span> \
wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex">
Thanks, Paul.<div>Actually I've already developed a module utilizing JPOS so it \
is easily configurable by xml configuration. I still have no idea how to integrate it \
with WSO2 ESB. Is it possible to create a new customized TCP Transport Module and \
attach it to WSO2 ESB? If yes, please give me any guidance to write the customized \
transport modules :-)</div>
<div><div>
<div><br><div class="gmail_quote">On Mon, Sep 17, 2012 at 12:28 PM, Paul Fremantle \
<span dir="ltr"><<a href="mailto:paul@wso2.com" \
target="_blank">paul@wso2.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
Lucky<div><br></div><div>You might well be able to use the TCP transport together \
with an ISO 8583 library like this to parse the messages: <a \
href="https://github.com/vikrantlabde/iso8583-Java" \
target="_blank">https://github.com/vikrantlabde/iso8583-Java</a></div>
<div><br></div><div>If not there are people who will help you figure out how to write \
a transport here :-)</div><div><br>Paul<br><br><div class="gmail_quote"><div><div>On \
17 September 2012 06:08, Lucky Haryadi <span dir="ltr"><<a \
href="mailto:xzorax89@gmail.com" target="_blank">xzorax89@gmail.com</a>></span> \
wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"><div><div><div> <p>I want to create a new transport \
processor on WSO2 ESB. This transport is to provide ISO 8583 message processing and \
transform Raw TCP to SOAP message, vice versa. On the source code, there is a
transport management object and inherited by several transport service
class such as JMS, HTTP, HTTPS, etc. I have several questions:</p>
<ol>
<li>How the transport management object works?</li>
<li>Is that possible to recode TCP service source code and redeploy with my \
customized actions?</li> </ol>
<p>Thanks.</p></div>
<br></div></div>_______________________________________________<br>
User mailing list<br>
<a href="mailto:User@wso2.org" target="_blank">User@wso2.org</a><br>
<a href="http://wso2.org/cgi-bin/mailman/listinfo/user" \
target="_blank">http://wso2.org/cgi-bin/mailman/listinfo/user</a><br> \
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Paul \
Fremantle<br>CTO and Co-Founder, WSO2<br>OASIS WS-RX TC Co-chair, VP, Apache \
Synapse<br><br>UK: <a href="tel:%2B44%20207%20096%200336" value="+442070960336" \
target="_blank">+44 207 096 0336</a><br>
US: <a href="tel:%2B1%20646%20595%207614" value="+16465957614" target="_blank">+1 646 \
595 7614</a><br><br>blog: <a href="http://pzf.fremantle.org" \
target="_blank">http://pzf.fremantle.org</a><br>
<a href="http://twitter.com/pzfreo" target="_blank">twitter.com/pzfreo</a><br><a \
href="mailto:paul@wso2.com" target="_blank">paul@wso2.com</a><div><br></div><div><a \
href="http://wso2.com" target="_blank">wso2.com</a> Lean Enterprise Middleware<br>
<br>Disclaimer: This communication may contain privileged or other confidential \
information and is intended exclusively for the addressee/s. If you are not the \
intended recipient/s, or believe that you may have received this communication in \
error, please reply to the sender indicating that fact and delete the copy you \
received and in addition, you should not print, copy, retransmit, disseminate, or \
otherwise use the information contained in this communication. Internet \
communications cannot be guaranteed to be timely, secure, error or virus-free. The \
sender does not accept liability for any errors or omissions. </div>
<br>
</div>
</blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Paul \
Fremantle<br>CTO and Co-Founder, WSO2<br>OASIS WS-RX TC Co-chair, VP, Apache \
Synapse<br><br>UK: <a href="tel:%2B44%20207%20096%200336" value="+442070960336" \
target="_blank">+44 207 096 0336</a><br>
US: <a href="tel:%2B1%20646%20595%207614" value="+16465957614" target="_blank">+1 646 \
595 7614</a><br><br>
blog: <a href="http://pzf.fremantle.org" \
target="_blank">http://pzf.fremantle.org</a><br><a href="http://twitter.com/pzfreo" \
target="_blank">twitter.com/pzfreo</a><br><a href="mailto:paul@wso2.com" \
target="_blank">paul@wso2.com</a><div>
<br></div><div><a href="http://wso2.com" target="_blank">wso2.com</a> Lean Enterprise \
Middleware<br><br>Disclaimer: This communication may contain privileged or other \
confidential information and is intended exclusively for the addressee/s. If you are \
not the intended recipient/s, or believe that you may have received this \
communication in error, please reply to the sender indicating that fact and delete \
the copy you received and in addition, you should not print, copy, retransmit, \
disseminate, or otherwise use the information contained in this communication. \
Internet communications cannot be guaranteed to be timely, secure, error or \
virus-free. The sender does not accept liability for any errors or omissions. </div>
<br>
</div></div></div>
</blockquote></div><br></div>
_______________________________________________
User mailing list
User@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/user
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic