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 <[email protected]> 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 <[email protected]> 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 <[email protected]> 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 <[email protected]> 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 >>>> [email protected] >>>> 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 >>> [email protected] >>> >>> 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 > [email protected] > > 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. > >
_______________________________________________ User mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/user
