>There is a reason I typically stay away from x.0 releases. WSO2 Carbon based WSAS is showing me again why. In general if you are implementing simple web services it works fine, and are generating basic Axis 2 1.4 based clients and server applications. The problems come in when you start to implement or test some of the more advanced enterprise level features.
The issue with the WS-Reliable Messaging implementation in WSAS 3.0.x is that it’s not based on an official release of the Sandesha2 1.3 jars. The code is based on a branch from the head of the Sandesha2 repository. This in general I do not have an issue with, however, there appears no way to generate ALL of the necessary client side JARs and MARs that are needed. In particular, I have not found the necessary MAR for Sandesha2. Supposedly this is supposed to be available when running the build.xml file found in the bin directory. However, this does not seem to be available in any of the directories that it should be.
Without the necessary client side JARs and MARs it’s impossible to resolve the compatibility issues without going to Apache, and checking out the source, then building it myself. Not a step that should be necessary.
Eclipse Web Tools for WSAS:
Unfortunately this is a big strike against the WSAS Tools. Taking a very basic WSDL, it will not complete the client side generation of that WSDL when it is targeted for a WSAS server. It stops and complains that it can’t find a necessary Axis 2 jar file. Again, shouldn’t this all be included with the WSAS tools when the plugins were installed?
Also, it would be nice if it would ask if I was doing WS-ReliableMessaging so that the appropriate MAR file can be copied for me. Yes, I have opened bugs regarding these problems with WSo2.
The sad thing is that I have some people interested in WSO2 because of it’s claim of easy configuration and implementation of some enterprise level features like WS-ReliableMessaging, WS-Policy, and WS-Addressing. It’s just appears that this needed a bit more time to bake or more public testing before releasing this product. I work for a standards organization, and this would be a great way for us to test and show interoperable implementations of our web services specifications, but at the moment I can not get by the most basic of errors with out jumping through extrodinary hoops.
I’ll probably back down to WSAS 2.3, which seemed to be a bit more stable, and hope that WSAS improves. If the WSAS developers want to provide me with a way to work with them and test out the problems I’m having, I’m more than willing to do so. In fact, I would invite them to show me how to get a STAR Web Service communicating with WSAS 3.0, for an upcoming demonstration we need to do. Any takers?