Re: Doc/Literal support in axis

[Dennis Sosnoski]

1.2 alpha appears to have a variety of problems. I was not able to use 
it directly for either rpc/encoded or doc/literal in some testing I'm 
doing, though I think the problems with both have been solved in the 
current CVS code. Until the developers come out with a 1.2 beta version 
that includes current CVS fixes I suggest you build your own from CVS if 
you want to work with the 1.2 code.

I *have* been able to get a recent version of the CVS code to generate 
Java classes from the WSDL for a doc/literal service. If you want to 
implement a doc/literal service on Axis that's probably the way to go - 
get or build a valid WSDL for the service and generate Axis code from that.

 - Dennis

Wei Hsu wrote:

Hi all,

 

I am currently in the process of modifying a RPC/Encoded web service 
to use RPC/Literal instead.  But while reading about interoperability 
issues, I realized that .NET among others does not support 
RPC/Literal, so I am looking to use doc/literal instead.  But I keep 
reading about how Axis 1.1 does not really support doc/literal - so 
what are some known issues with 1.1 and doc/literal?  Are they 
problems more with server side or client side?

 

Has anyone tried working with Axis 1.2 alpha for doc/literal support?  
What are some known advantages/disadvantages of using Axis 1.2 alpha 
over Axis 1.1? 

 

I'd appreciate any insight or information. Thanks a lot!

 

- Wei