Sounds good! However, why do you need a StompMessageReceiver? You should only need a listener, a sender, a message formatter and a message builder. The listener and the message builder combine to deliver a MessageContext into the AxisEngine and in the other direction the sender and formatter write one to the wire.
Sanjiva. On Thu, Dec 24, 2009 at 2:27 AM, Dunith Dhanushka <duni...@gmail.com> wrote: > Hi folks, > > I just got an idea to write a new transport for axis2 based on Stomp > protocol. Stomp can be used to deal with any Stomp supported message broker > (like Apache ActiveMQ) to send and receive messages. > > Since Stomp is very simple protocol, many scripting languages such as > Ruby,PHP and python heavily use it for dealing with message brokers. So if > Axis2 has Stomp support, they would send SOAP messages into axis2 through > Stomp supported broker and they will leverage the performance of axis2 > engine, when it comes to consume web services. > > As a start, I designed some basic set of classes for the Stomp transport > > * StompListener - for listening to incoming Stomp messages > * StompConnection - represents a connection between axis2 and the > broker. > * StompMessageReceiver - worker thread that handles all incoming Stomp > messages. uses a shared worker thread pool > * StompConstants - constants specific to Stomp is defined here > * StompSender - implements the TransportSender interface > * StompUtils - utilities > > So I would like your feedbacks about this implementation. > > Cheers! > Dunith Dhanushka > > > > -- Sanjiva Weerawarana, Ph.D. Founder, Director & Chief Scientist; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ Blog: http://sanjiva.weerawarana.org/
