Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Received-SPF: pass (hermes.apache.org: domain of atmanes@gmail.com designates
 64.233.184.197 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=mKK9TDcag6hjZwdPGEoqiInG5FLTbhkaRDzHp42FBOprXPe0GVYhXTQmD4QKF4mwovI9NAe7xA796TrQ3dYe7mlLQA/84pCIPVRb5tfuSj75tKFNMfo+85J0kncReRKQsrVZwoROPZhtDfvDHghg8HDduShPO9GhmSKWelMiciA=
Message-ID: <bf414ee6050604041542a4e537@mail.gmail.com>
Date: Sat, 4 Jun 2005 07:15:02 -0400
From: Anne Thomas Manes <atmanes@gmail.com>
Reply-To: Anne Thomas Manes <atmanes@gmail.com>
To: James Taylor <taylorjw@tcd.ie>, axis-user <axis-user@ws.apache.org>
Subject: Re: communication styles issue
In-Reply-To: <1117837810.42a0d9f2dbbf5@mymail.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <1117812789.42a0783537e2b@mymail.tcd.ie>
	 <1117813099.42a0796b6bad4@mymail.tcd.ie>
	 <bf414ee60506031226622ea9f@mail.gmail.com>
	 <1117837810.42a0d9f2dbbf5@mymail.tcd.ie>

James,

If you want to use JAXM, then you can't use Axis. As I said, Axis
doesn't support it. If you want to use a messaging style interface
with Axis, you must use Axis "message" style.

You should use JAXM or the Axis "message" style if your application is
manipulating XML programmatically using DOM. (It doesn't support SAX
or XML as strings.)

You don't use wsdl2java when using the JAXM or "message" style
programming interface. These messaging style interfaces aren't
WSDL-aware. Your application is responsible for constructing the SOAP
Body contents as a DOM, then it uses the messaging API to construct
the SOAP message frame, then it adds the Body contents, then it uses
the messaging API to send the message.

Anne

On 6/3/05, James Taylor <taylorjw@tcd.ie> wrote:
>       Thanks for your reply Anne and look at the link to your blog to try=
 and
> get a better idea about axis wrapped style. If I am to use JAXM to send
> messages does this involve a different developement process then wsld2jav=
a.
> Like should one then use the calls to invoke methods?
>       Regards,
>               James.
> Quoting Anne Thomas Manes <atmanes@gmail.com>:
>=20
> > JAXM is equivalent to the Axis "message" style service. Axis doesn't
> > implement JAXM. (It's not a required component within J2EE 1.4.)
> >
> > See my previous post on the issues associated with trying to return
> > XML as a string.  (short answer: don't do it -- your application
> > should return Java objects, and then Axis will serialize them into XML
> > for you). Note that an XML string is NOT the same as an XML document.
> > From a Java perspective, there's a big difference between a String
> > type and a Document type.
> >
> > Regarding "styles" -- it's important to distinguish between Axis
> > programming styles ("rpc", "wrapped", "document", and "message") and
> > the WSDL message encoding styles ("rpc" and "document").
> >
> > Here a quick mapping between the style types:
> >
> > Axis "rpc" style generates WSDL rpc/encoded. The programming interface
> > looks and feels like RMI (invoke methods on an interface; input zero
> > or more parameters, get back a return value)
> >
> > Axis "wrapped" style generates WSDL document/literal conforming to the
> > "wrapped" convention. The programming interface is identical to "rpc"
> > style. This style gives you the best interoperability with .NET.
> >
> > Axis "document" style generates WSDL document/literal. The programming
> > interface is similar to "rpc" and "wrapped", but the input paramenters
> > must be assembled into a single object.
> >
> > Axis "message" style lets the application build the SOAP message
> > programmatically using DOM. Typically you would only use the "message"
> > style with document/literal.
> >
> > In Axis 1.x, all styles except "message" style use a synchronous,
> > request/response message exchange pattern (MEP). The "message" style
> > can support both request/response and one-way MEPs.
> >
> > Anne
> >
> > On 6/3/05, James Taylor <taylorjw@tcd.ie> wrote:
> > > Another one:
> > > 4. If i want to develope a web service using jaxm will I have to use
> > something
> > > other then axis's wsdl2java as this produces rpc style stubs to absta=
rct
> > the
> > > xml?
> > >
> > > Quoting James Taylor <taylorjw@tcd.ie>:
> > >
> > > > Hey folks,
> > > >           my service takes data from the
> > > > client, queries a database but instead of sending back a resultset =
of
> > found
> > > > object sends back an xml String result which is basically a xml doc=
ument.
> > > >          1. The binding style in the wsdl says rpc - is this a
> > synchronous
> > > > communication style?
> > > >          2. Should I use document-literal style and how would I imp=
lement
> > > > this?
> > > >          3. Could I achieve a synchronous document-literal style us=
ing
> > rpc or
> > > > should I use jaxm for this.
> > > >          Just a bit confused on styles I guess.
> > > >          Regards,
> > > >                  James.
> > > >
> > > > --
> > > > Between the question and the answer lies free will
> > > >
> > >
> > >
> > > --
> > > Between the question and the answer lies free will
> > >
> >
>=20
>=20
> --
> Between the question and the answer lies free will
>