axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Agarwal, Naresh" <>
Subject RE: Antwort: RE: Axis doc/lit - impossible?
Date Thu, 09 Oct 2003 09:20:46 GMT

I agree that wrapped/literal solves some of the problem, which are there in doc/literal but
still wrapped/literal services are NOT interoperable with .NET clients.

Axis uses *soapenc:arrayType*  for encoding the *arrays* in wrapped/literal type of services,
is NOT expected in wrapped/literal. 
Due to this fact, axis services, which returns array _CAN_NOT_ be consumed by .Net clients.

Have a look at the bug and 
the discussion thread

-----Original Message-----
From: Oliver Wulff []
Sent: Thursday, October 09, 2003 10:29 AM
Subject: Antwort: RE: Axis doc/lit - impossible?


run WSDL2Java for the WSDL published at

You'll notice that the namespaces are missing. It generates:
  _return.value = (com.xmlbus.berechtigung.xsd.OrgEinheit_T)_output.get(new

  javax.xml.namespace.QName("", "return"));
instead of
  _return.value = (com.xmlbus.berechtigung.xsd.OrgEinheit_T)
  javax.xml.namespace.QName("", "return"));


Oliver Wulff
Zürich Versicherungs-Gesellschaft
IA4, CoC Middleware
Postfach, 8085 Zürich
Telefon: +41- 1 628 58 07
Fax: +41 - 1 623 58 07

                      (HP-MountainView         An:      "''" <>
                      ,ex1)"                   Kopie:                                    
                      <>         Thema:   RE: Axis doc/lit - impossible?
                      09.10.2003 01:38                                                   
                      Bitte antworten                                                    
                      an axis-user                                                       

Hi List,

I was able to generate perfectly working client classes with WSDL2Java from
an SAP wsdl file which specifies a soap binding style of 'document' and
body use="literal".

So is the issue that doc/lit support on the server side is 'impossible'?

Just Curious,


PS - If anyone wants, I can send them the WSDL.

-----Original Message-----
From: Cory Wilkerson []
Sent: Tuesday, October 07, 2003 12:10 PM
Subject: RE: Axis doc/lit - impossible?

I concur.  Doc/literal support was an afterthought when Axis was put

-----Original Message-----
From: Mike Perham []
Sent: Tuesday, October 07, 2003 2:02 PM
Subject: RE: Axis doc/lit - impossible?

That's been our finding also.  Axis supports rpc/encoded very well.
Anything else is just an exercise in frustration.  We wound up writing
our own doc/lit SOAP stack because Axis just didn't work and Sysinet was
too expensive and proprietary.


-----Original Message-----
From: Dennis Sosnoski []
Sent: Tuesday, October 07, 2003 1:28 PM
To: axis-user
Subject: Axis doc/lit - impossible?

Mitch Gitman has an article up on JavaWorld talking about Web service
In the second page he covers several attempted approaches to
implementing a doc/lit service using Axis (none of which work properly)
and comes to the conclusion that "while Axis purports to support
document/literal, it actually doesn't."

Any comments? I've played around with doc/lit using Axis myself and ran
into problems, but assumed I could find a work-around with enough effort
(probably by avoiding WSDL2Java and Java2WSDL, and supplying my own WSDL
for the service - at which point Axis isn't really adding a lot of
value). Mitch says that Axis flat out doesn't support doc/lit, though he
appears to only be working with the W2J/J2W tools.

  - Dennis

View raw message