
0.9
WSO2 Mercury is a WS-ReliableMessaging specification implementation that uses Apache Axis2/Java as the SOAP engine.

1.5
WSO2 Identity Solution is a set of Relying Party components and an Identity Provider to enable CardSpace and OpenID authentication.

1.0
WSO2 WSF/Spring integrates Apache Axis2 into Spring and provides a Code First approach to create Web Services for the Spring user.

1.2.1
WSO2 WSF/PHP, a PHP extension used to provide and consume Web services in PHP.

1.0.2
WSO2 Mashup Server is a platform for creating, deploying, and consuming Web services Mashups.

2.2.1
WSO2 WSAS is an enterprise ready Web services engine powered by Apache Axis2. It is a lightweight, high performing platform for SOA

1.0
WSO2 Registry is a Web 2.0 style registry and repository for storing resources and metadata.

1.6
WSO2 ESB is a lightweight, XML and Web services centric ESB, based on Apache Synapse and Axis2.

1.0.0
WSO2 WSF C++, a binding of WSO2 WSF/C into C++ is an extension for consuming Web Services in C++.

0.6
WSO2 User Manager is a library enabling user authentication and authorization in applications to be handled in a homogeneous manner.

1.2.0
WSO2 WSF/C is a framework based on Apache Axis2/C, Rampart/C and Sandesha2/C for providing and consuming Web services in C.

1.0.0
WSO2 WSF/Ruby, a binding of WSO2 WSF/C into Ruby is an extension for consuming Web Services in Ruby.

1.0.0
WSO2 WSF/Perl, a binding of WSO2 WSF/C into Perl is a Perl extension for consuming Web Services in Perl.
With just using Axis2 you
With just using Axis2 you can not tell a number of retries that Axis2 use before it throws an exception. One thing you can do is you can write your client so that it will call your stub few times and throw exception each time it get the connection exception. Or else we can use something like Reliable messaging mechanism. That that layer will taking care of that , and even you can configure number of re tries you want to make.
Hmm, maybe it's just me but
Hmm, maybe it's just me but this seems like a pretty big shortcoming in Axis2... of course I'm not terribly familiar with the internal workings but it doesn't seem like it should be that complicated to simply set the retry count :(
Also I don't believe I can simply catch the ConnectException; the generated stub method call only throws a RemoteException which occurs after 3 timeouts (ConnectExceptions). These appear to be caught internally in the client stub. Currently we're generating the client using the WSDL2Code feature of WSAS and I'd rather not have to make manual changes if at all possible.
Anyway thanks for the reply; if anyone else has any other suggestions they would still be appreciated :D
This is not a major
This is not a major shortcoming. The stub & stub generation tools (we will have to add another option to specify the retries) have been kept as simple as possible. If you need to do advanced stuff, you always have the option of handling it in your client which calls the stub or using WS-RM.
Regards
Afkham Azeez