'Apache SOAP 3.0 (Axis)'

Question

How do i configure the proxy generator to use 'Apache SOAP 3.0 (Axis)'?

Answer 1

The interop with OC4J904 adds a pretty major feature with its untyped support. If you look through the list here you will see almost 80-90% of the questions to do with interop have to do with untyped. So I am hoping that this change will solve the most prominent use cases. There is one unsupported case in the preview that has now been fixed for production and that is support for arrays with untyped elements (e.g. the SOAP messages has the array definition through SOAP encoding but the contents of the array are untyped).
Going forward to the JavaOne timeframe we expect to be previewing our JAXRPC implementation on OC4J that will have our first step towards WS-I compliance - as both sides MS and the Java camp both are working heavily in the WS-I organization and expect to have WS-I compliant engines, I believe/hope this will be the next big step towards interop between platforms.
So as for your question on Apache AXIS ... if you are planning to stay with the integrated Oracle stack that is evolving pretty tightly with the standards, the answer would be no - stick with Oracle's stack. Especially since development right now is heavily focussed around JAX-RPC support.
However, there are things that AXIS has today that we do not have so there may be tactical reasons to go to it today. For deployment of AXIS on OC4J you shouldn't have to use Tomcat at all ... in the 1.0 and the 1.1 RC there is essentially a WEB-INF directory with all the required files in it - the lazy way to test it out without thinking at all is to create an empty J2EE application called "XXX" where XXX is some meaningful name, deploy XXX to OC4J and then drop in a new WEB-INF directory from AXIS in there and away you go.
Mike.