Axis JWS Document/Literal

Hi,

I am fairly new to using Axis and have hit on upon a roadblock for which I couldn't find anything on the net. I was hoping that someone here migh thav encoutered a similar issue and know the solution.

I have a JWS file which is hosted on a Tomcat server. The client of this service is a .NET client. Last week we started getting issues when we tried to return collections/java beans from our new service to the .NET client.

After looking around a bit, I found that the format that I needed to use is document/literal instead of the default rpc/encoding.

Here's the problem, I can't find any configuration to change the format from the default rpc/encoding to document/literal for a JWS file (wherein the WSDL is generated automatically).

P.S. I am using Axis 1.4 for development.

Appreciate any inputs on the same.

Cheers!!!

Hi,

Firstly welcome to Javaranch..

You must have missed our naming policy on the way in. In short, your displayed name must be your real (or at least real-sounding) first and last name separated by a space. You can change your displayed name here. Thank you for your prompt attention.

Regarding your question: If you are using javabeans, then you must specify the typemapping for it so that .NET kind of clients can interpret the javabeans...
for more info please see this article
Using Complex Type
Thank you.
Regards
Balaji

Balaji,

Thanks for pointing out the naming policy, I've changed my profile name accordingly.

Also, thanks for pointing out at the article which had some very uselful information on Axis & interoperability.

However, I still have two questions:

1. Is there a way to return doc/literal format from a JWS file in Axis 1.4?

2. Does .NET client even support rpc/encoding? If yes, what changes does the .NET client have to make for the same?

Thanks!!!

>>1. Is there a way to return doc/literal format from a JWS file in Axis 1.4?

With my last revision, JWS doesnt support it. The best way is to use axis config to tell what format you want to support.

>>>2. Does .NET client even support rpc/encoding? If yes, what changes does the .NET client have to make for the same?

No need to make any changes, just give the wsdl to the .NET web services wizard, it will take care of everything.