On 10/29/07, Pantvaidya, Vishwajit <[EMAIL PROTECTED]> wrote: > > I am generating the interface (-ssi option) and none of the methods > generated there with Axis2 1.3 are defined as throwing RemoteException (as > was the case in Axis1). My web service implementation methods which are > coded to match the Axis1 generated interface throw RemoteException. So now > after wsdl2java with Axis2, I have compile time issues as the method > signature does not match. >
ok you are talking about the server side. why should a skelton method throws a RemoteException? I think throwing RemoteExceptions from the skelton classes is wrong. Amila. ------------------------------ > > *From:* Amila Suriarachchi [mailto:[EMAIL PROTECTED] > *Sent:* Monday, October 29, 2007 5:28 AM > *To:* [email protected] > *Subject:* Re: [Axis2] How to specify wsdl operation so that wsdl2java > generates method throwing java.lang.RemoteException > > > > generated stub method already throws this exception isn't? > > eg. > public java.lang.String Echo( > > java.lang.String echoIn7) > > > throws java.rmi.RemoteException > > { > > Amila. > > On 10/26/07, *Pantvaidya, Vishwajit* < [EMAIL PROTECTED]> wrote: > > I am migrating to Axis2 1.3 from Axis1. I have existing code that relies > on the webservice methods throwing java.lang.RemoteException. Is it > possible to specify an operation in the wsdl, such that, wsdl2java generates > methods that throw RemoteException? I know that is not the best way to do it > – but just for compatibility with existing code. > > > > Thanks, > > > > Vish. > > > > > -- > Amila Suriarachchi, > WSO2 Inc. > -- Amila Suriarachchi, WSO2 Inc.
