DOCUMENT/LITERAL certainly does work! Mostly anyway. I recently submitted a patch (bug <a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23664 ">23664</a>) that fixed a deserialization problem on the client side with operations not containing any in params.
Here is a contrived example project doing DOCUMENT/LITERAL with Castor plugged in to handle the type mapping of params and return types. <a href="http://www.maring.org/CustomTypeMapper.zip";>CustomTypeMapper.zip</a> (8MB) The project starts with data types defined as XSDs, a WSDL, a functional SOAPBindingImpl, and a functional TestCase. Out of it comes a deployable war. There are also contained therein a couple of handy stylesheets that I wrote to convert the generated deploy.wsdd into server-config.wsdd and client-config.wsdd. I had no interest in the Java2WSDL process since I wanted my Castor generated data types to reside in a seperate namespace. Cheers. Steve Maring --- Oliver Wulff <[EMAIL PROTECTED]> wrote: > > > > > Maybe, it's not mentioned if it's a bug in > document/literal for Axis 1.1 > rc2. Probably, it didn't work at all (also for > rpc/encoded) in rc2 but it > has been fixed only for rpc/encoded in Axis 1.1. > I sent my problem some weeks ago and got the > information that this seems to > be a bug and I should raise a request to bugzilla. > > Oliver > > ****************************************************************** > 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 > E-Mail: mailto:[EMAIL PROTECTED] > > > > > > Davanum Srinivas > > <[EMAIL PROTECTED]> An: > [EMAIL PROTECTED] > > Kopie: > 08.10.2003 13:05 > Thema: Re: Antwort: RE: Axis doc/lit - impossible? > Bitte antworten > > an axis-user > > > > > > > > > > Oliver, > > is this a duplicate of > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20054? > > -- dims > > --- Oliver Wulff <[EMAIL PROTECTED]> wrote: > > > > > > > > > > I had the same problem with document/literal and > raised the bug 21824. > > Hope, it will be fixed soon, because I have to > manually fix the > namespaces > > in the generated code. > > > > Oliver > > > > > ****************************************************************** > > 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 > > E-Mail: mailto:[EMAIL PROTECTED] > > > > > > > > > > Davanum Srinivas > > <[EMAIL PROTECTED]> An: > [EMAIL PROTECTED] > > > Kopie: > > 08.10.2003 12:13 > Thema: RE: Axis doc/lit > - impossible? > > Bitte antworten > > an axis-user > > > > > > > > > > > > > > java2wsdl works too (maybe a bit flaky)...In Axis > terms, you need to use > > the "wrapped" mode. See > > > http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/Wrapped. > The > > WHOLE confusion is > > because have a flag "-y" in java2wsdl that can > take DOCUMENT/WRAPPED/RPC. > > DOCUMENT here means that > > the the deployer/programmer knows exactly what to > do in wsdd and Axis > > should not wrap or unwrap > > the method parameters. WRAPPED is used when you > need Axis to do doc/lit > and > > you don't want to muck > > around with wsdd. See > > > http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/Wrapped > for > > pointers to previous discussions etc. > > > > -- dims > > > > --- Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > > Dims, > > > > > > Perhaps the team's assessment of the desired use > cases for doc/literal > > was > > > a bit too limited. java2wsdl should be capable > of generating a > > doc/literal > > > WSDL definition from a Java class. > > > > > > Thanks, > > > Anne > > > > > > At 02:48 AM 10/8/2003 -0700, you wrote: > > > >I repeat myself... > > > > > > > >The Best Use case for doc/lit that Axis 1.1 > supports is when you start > > > >with an existing WSDL and > > > >run WSDL2Java on it and use the generated code. > If you have problems > > with > > > >this, open up a bug > > > >report with sample code. > > > > > > > >Thanks, > > > >dims > > > > > > > >--- Cory Wilkerson <[EMAIL PROTECTED]> > wrote: > > > > > I concur. Doc/literal support was an > afterthought when Axis was > put > > > > together. > > > > > > > > > > -----Original Message----- > > > > > From: Mike Perham > [mailto:[EMAIL PROTECTED] > > > > > Sent: Tuesday, October 07, 2003 2:02 PM > > > > > To: [EMAIL PROTECTED] > > > > > 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. > > > > > > > > > > mike > > > > > > > > > > -----Original Message----- > > > > > From: Dennis Sosnoski > [mailto:[EMAIL PROTECTED] > > > > > 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 > > > > > styles > > > > > ( > http://www.javaworld.com/javaworld/jw-10-2003/jw-1003-wsstyles.html? > > ). > > > > > 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 === message truncated === __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
