axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Chen" <>
Subject RE: Disable multiref on the server side
Date Sun, 06 Jun 2004 23:43:04 GMT
Thanks for the information, Venky.

But I have a problem here:

I always remove this file after a re-build of the code, which includes
running org.apache.axis.wsdl.WSDL2Java tool to generate Java stubs from
the WSDL file and corresponding deploy.wsdd file.
I then start Tomcat to load Axis and run org.apache.axis.client.AdminClient
to re-generate a new server-config from all the deploy.wsdd files.
There is no hand-editing of server-config.wsdd involved.

Is there a way to make AXIS always generate the new server-config with
this 'sendMultiRefs' turned off?

-----Original Message-----
From: Jayaraman, Venkatesh []
Sent: Sunday, June 06, 2004 1:41 PM
Subject: RE: Disable multiref on the server side

It is the option in server-config.wsdd file

   <parameter name="sendMultiRefs" value="false"/>

-----Original Message-----
From: Alex Chen [] 
Sent: Saturday, June 05, 2004 6:17 PM
Subject: Disable multiref on the server side

I am using AXIS (Java, as a server) and gSOAP (C, as a client) in RPC
style communication.

If the encoding style is set to
<soap:body use="encoded"
encodingStyle="" .../>

gSOAP client is able to send a SOAP object (C structure on the client
side) to the AXIS, and the server is able to deserialize the message
into the binding class generated from the WSDL. But when the server
returns a SOAP object, the XML message contains 'multiref id=' tags in
the message body.  This causes the gSOAP client to choke because it
cannot decode it.

I also find that if the encoding style is set to
<soap:body use="literal" />

the XML message generated by the AXIS server will not have 'multiref'
tag. But if the client (gSOAP side) sends a SOAP object, as in the above
case, the AXIS server cannot decode the message, because the gSOAP puts
namespace tags and other stuff in the message it generates.

In a nutshell, in 'encoded' case, AXIS can decode messages in encode
style, but generated messages with 'multiref' tags.  In 'literal' case,
AXIS does not generate messages with 'multiref' tags but fails to decode
messages that are in 'encoded' form.

I have looked at the mailing archive and only find discussion in
disabling the PROP_DOMULTIREF property on the client side.  How do I
turn off this property on the AXIS server side so that it does not
generate multiref tag in the reply message?

Any help is greatly appreciated.


View raw message