Okay, thanks. I'll take a look an' see what I can come up with. So does that mean I can't use Axis2 to connect to my Axis stuff? Or do I have to change the WSDL and then rebuild the Axis stuff to use the new WSDL?
I'd like to do the integration with Axis2 in the way that will have the least impact on my legacy Axis stuff. On Fri, Oct 3, 2008 at 11:42 PM, Nadun Herath <[EMAIL PROTECTED]>wrote: > Hi Bjorn > > Problem is Axis2 doesn't support rpc/encoded style. You have convert your > wsdl to doc/literal. > > Hope this will help > > http://www.mail-archive.com/[email protected]/msg31438.html > > http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html > > http://pzf.fremantle.org/2007/05/handlign.html > > > Thanks > > > > > Nadun Malaka Herath > Department of Computer Engineering > University of Peradeniya > > > ----- Original Message ---- > From: Bjorn Townsend <[EMAIL PROTECTED]> > To: [email protected] > Sent: Saturday, October 4, 2008 2:02:43 AM > Subject: Re: Axis vs Axis2 > > > On Oct 3, 2008, at 10:58 AM October 3, Bai Shen wrote: > > > Okay, so I've recently started using Axis2 after having used Axis > > for a while. I have a wsdl that works fine in Axis(although it does > > have a few idiosyncrasies). However, I can't seem to get it to work > > at all in Axis2. I read the migration guide, but that seemed more > > about how the two versions handle creating skeletons. > > > > The whole point of web services is to keep things platform > > independent, right? So why would a wsdl work with Axis, but not > > Axis2? > > Are you using RPC-encoded? If so, I don't believe Axis2 supports it, > and it is the default for Axis 1. > > Bjorn > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > >
