Nadun, Sounds interesting. Probably you will have to start thinking about two fundamental questions:
1) Axis2 always represents messages as XML (more precisely a SOAP infoset). So you need to decide how this mapping will be done. Most protocols we already support exchange binary or text messages (a notable exception is the FIX transport in Synapse) for which this is fairly easy. I don't know much about JavaSpaces, but if it imposes its own structure on the messages, then you need to define a mapping to and from XML. 2) You need to analyze how incoming messages would be dispatched to services. The existing transports fall into two categories: - Transports such as HTTP that accept messages on a single "protocol endpoint" (a TCP port in the case of HTTP) and than use Axis2 dispatchers to dispatch to the right service (typically based on the request URI). - Transports such as mail and JMS on the other hand predispatch messages: the transport itself maintains the mapping between protocol endpoints (email accounts, JMS destinations, etc.) and the services. If that is the right model for JavaSpaces, then you can build your transport on top of AbstractTransportListener (from the axis2-transport-base module in the WS-Commons Transport project). Hope that helps. Regards, Andreas On Tue, Jun 2, 2009 at 15:34, Nadun Herath <nadunher...@gmail.com> wrote: > I intend to develop a Javaspace transport to Axis2 as a university project. > I am really grateful for any suggestions, ideas. > Thank you. > > http://java.sun.com/developer/technicalArticles/tools/JavaSpaces/
