Sandesha2 > Java

The Apache Sandesha2 project was started to provide a reliability layer for Apache Axis2. Sandesha2 is well on its way past the 1.2 stage and has gathered a faithful user and developer community around it. Chamikara Jayalath, a key contributor to the Sandesha2 project, speaks about the product and the main features of it.

According to the WSRM specification Apache Sandesha2 has to send several control messages back and forth during your application message exchange. When doing a two-way message exchange you need to be aware of certain details including additional configurations to perform this message exchange accurately. This tutorial by Chamikara Jayalath gives you an insight into those details.

The Axis2 client API allows you to pass various properties into the system using the Options object. The Options object is a part of the MessageContexts that are created for each invocation. The properties are used by the core Apache Axis2/Java engine or any other module that you deploy into it.

You can use Sandesha2 listeners to get notified when specific events happen in the Apache Sandesha2 system. You will most probably be registering your listener in the client code. Calling back could happen within any time of the execution of Sandesha2.

Apache Sandesha2 or rather any other WSRM implementation has to exchange several protocol specific messages with an endpoint with which you are trying to communicate reliably. Because of this, even though you may be doing only a single invocation from your client code Sandesha2 would most probably be exchanging several other messages as well. The amount of time that is taken for this depends on your system performance and on the quality of the network between you and the other endpoint.

Apache Sandesha2 reports can be used to get information from a running Sandesha2 system. Most of the times these reports will be requested through your client code. There are two kinds of Sandesha2 reports you can request for.