I’ve used Apache Axis (and its predecessor Apache SOAP) on a
few projects, and I’ve had nothing but good experiences with it. In my experience, it “just worked” when I needed to integrate with Active X and .NET applications.
One trick I learned, if you don’t want to hand code a bunch of XML Schema, was to first code the java interface, along with all the
supporting beans that you intend to pass back and forth, and run the whole thing through the Java2WSDL tool. This will produce a WSDL file which defines your service, and includes Schema for the beans you use.
Then run that WSDL file through the WSDL2Java tool. This will create “stubs” and “skeletons” for your service, along with deployment descriptors.
I’ve used Apache Axis (and its predecessor Apache SOAP) on a
few projects, and I’ve had nothing but good experiences with it. In my experience, it “just worked” when I needed to integrate with Active X and .NET applications.
One trick I learned, if you don’t want to hand code a bunch of XML Schema, was to first code the java interface, along with all the
supporting beans that you intend to pass back and forth, and run the whole thing through the Java2WSDL tool. This will produce a WSDL file which defines your service, and includes Schema for the beans you use.
Then run that WSDL file through the WSDL2Java tool. This will create “stubs” and “skeletons” for your service, along with deployment descriptors.