Java for soap is quite extensive and generally works extremely well. We have used it in many places with good results. The only major problem is, as you discovered, trying to deal with discrepancies when calling complex services designed specifically for .NET.
I don't suppose you have specific recommendations as far as this goes? I'm lost in a sea of libraries and options. As I mentioned, I'm trying to work against the MapPoint webservice, but I've had no luck in creating even the most basic client with axis2 against their wsdl.
wsdl2java has worked really well for any WSDL I've ever had to work against (consuming fairly rich both Java and .Net web services from Java).
Note that there's been a fair bit of resistance to Axis2, with a lot of people preferring to stay on 1. I believe they changed the entire team from 1 to 2.
Comments
Java for soap is quite extensive and generally works extremely well. We have used it in many places with good results. The only major problem is, as you discovered, trying to deal with discrepancies when calling complex services designed specifically for .NET.
I don't suppose you have specific recommendations as far as this goes? I'm lost in a sea of libraries and options. As I mentioned, I'm trying to work against the MapPoint webservice, but I've had no luck in creating even the most basic client with axis2 against their wsdl.
Have you looked at wsdl2java? http://ws.apache.org/axis/java/user-guide.html#WSDL2JavaBuil...
wsdl2java has worked really well for any WSDL I've ever had to work against (consuming fairly rich both Java and .Net web services from Java).
Note that there's been a fair bit of resistance to Axis2, with a lot of people preferring to stay on 1. I believe they changed the entire team from 1 to 2.