Hi Brian
You may be mixing a bit things here. You need stubs and
deployment on the SERVER side in Axis, not on the
CLIENT side. WSIF is a client side framework and
uses the client side code of Axis to serialize/deserialize
SOAP messages (mostly through the org.apache.axis.client.* and
related classes), if you forget about the Apache provider.
Axis definitely can be used on the client side without
WSDL2Java because...that's what WSIF is doing :) As long
as your complex types map to well behaved javabeans,
Axis is able to translate objects to SOAP and vice versa.
Agreed, depending of your particular problem, it could
be easier to use the WSIF interface than Axis, but I
believe the internals of the provider should not be
exposed on the WSIF upper layers.
/zog
> -----Original Message-----
> From: Brian Reynolds [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 26, 2004 5:38 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Newbie Q about SOAP responses
>
>
> Hi zog,
>
> Thanks for the feedback.
>
> I feel that the advantage of WSIF is that it can
> generate SOAP messages directly from WSDL, in contrast
> to Axis which requires the extra step of WSDL2Java to
> be executed. And I don't believe Apache SOAP has any
> WSDL support at all. WSIF also has a very nice
> interface - (again in comparison to Axis) no stubs
> strictly required, and no deployment - a distinct
> advantage.
>
> In regards to the parsing of the message, I don't
> believe your comment below is the case. The reason for
> this is that I have a vanilla Web Server (no Axis no
> Apache SOAP) firing back a SOAP response to the
> DynamicInvoker, I can see that the response
> information has been taken out, and returned (in the
> WSIFMessage variable) correctly. Therefore the WSIF
> piece _must_ do some level of parsing of the SOAP
> message.
>
> Does this make sense?
>
> Best Regards,
> Brian
>
> --- Jacques-Olivier Goussard <[EMAIL PROTECTED]> wrote:
> > Hi
> > It's not the first time someone asks for this. What
> > I
> > don't get is why you use WSIF if you need to access
> > the SOAP message ? WSIF power and flexibility is -
> > IMHO -
> > based on provider agnosticity. If you know you're
> > going
> > to access a SOAP-enabled service, why don't use
> > directly Axis (which BTW provides you with what you
> > need) ?
> > WSIF core does not parse the SOAP message, AXIS (or
> > Apache SOAP, depending on the chosen provider) does
> > it.
> > /zog
> >
> > > -----Original Message-----
> > > From: Brian Reynolds [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, February 25, 2004 1:53 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Newbie Q about SOAP responses
> > >
> > >
> > > Hi there,
> > >
> > > I'm a newbie getting involved with WSIF, and I'm
> > > trying out the DynamicInvoker sample (cool!). What
> > I
> > > would like to know is it possible to access the
> > "raw"
> > > SOAP response from the WSIFMessage variable
> > filled-in
> > > (after a call to executeRequestResponseOperation)
> > - or
> > > is it possible at all?
> > >
> > > My question is based on the assumption that the WS
> > > returns a SOAP response and the WSIF core will
> > parse
> > > this to retrieve the requested information. I
> > believe
> > > this is correct or ?
> > >
> > > Your feedback would be greatly appreciated.
> > >
> > > Regards,
> > > Brian
> > >
> > >
> > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > Yahoo! Mail SpamGuard - Read only the mail you
> > want.
> > > http://antispam.yahoo.com/tools
> > >
>
>
> __________________________________
> Do you Yahoo!?
> Get better spam protection with Yahoo! Mail.
> http://antispam.yahoo.com/tools
>
