Mitch,
searched the dev mailing list archives...did not find a single post from you :) would
have REALLY
appreciated a heads up/bug report/patch since you have been working on the article for
some time
:(
Do you have a few cycles to help us fix the problems? ("Axis 1.1 does not support, or
has bugs
with, a few essential aspects of literal use and document style."). Last check, there
were 13
major products that use Axis
(http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/AxisBeingUsed) and we
could really
use your help to fix problems in Axis 1.2.
thx,
-- dims
--- Mitch Gitman <[EMAIL PROTECTED]> wrote:
> The writer here. Dennis, thanks for mentioning the article. I do have to
> clarify one characterization of yours. Only a brief passage in the section on
> Axis covers Java2WSDL. Most of the rest of the section focuses on starting
> from external WSDLs, which run the continuum from being completely generated
> by another toolkit to being largely handwritten.
>
> Even with WSDL generation left out of the equation, Axis 1.1 does not support,
> or has bugs with, a few essential aspects of literal use and document style.
> One can read the article to see what I'm talking about.
>
> While I did mention message-style services in Axis, I did not attempt to
> produce a document/literal Web service by setting up a message-style service
> and then passing along the message to an external binding framework -- like
> Castor, JIBX, XMLBeans, a JAXB implementation. Nor did I cover plugging in
> custom serializers.
>
> Neither of these approaches is what was meant by the assertion that Axis 1.1
> supports document/literal. From a more practical and meaningful standpoint, it
> didn't make sense to tell user-developers to take such roundabout routes
> merely to get around the holes in Axis's built-in document/literal
> implementation.
>
> Davanum Srinivas <[EMAIL PROTECTED]> wrote:
>
> 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
>
> --- Mike Perham <[EMAIL PROTECTED]> wrote:
> > 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 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
> >
> >
>
>
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
>
>
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
