Yes, if you look at the autogenerated wsdl, you can see which soap action to set for which operation.
http://wso2.org/library/176 -- dims On 12/14/06, Ted Jones <[EMAIL PROTECTED]> wrote:
The soap action is set. Is this value being used to determine which operation to execute? Is there a way to force it to pick the method specified in the service.xml that uses the OMElement methodName(OMElement element) signature? Thanks, Ted -----Original Message----- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, December 14, 2006 1:50 PM To: axis-user@ws.apache.org Subject: Re: Axis 1.* to Axis2 Migration Question make sure you set the soap action correctly. -- dims On 12/14/06, Ted Jones <[EMAIL PROTECTED]> wrote: > Thanks for the response dims. The Axis 1.* implementation is such that > it does not matter what the method name is, as long as the signature > matches one if the expected method signatures. If the method name was > specified in the allowableMethods property, it would be executed. So > the operation name did not have to match the method name. Is this > still the case? The reason I ask is because I am getting an Operation > not found exception. > > Thanks for your help, > Ted > > -----Original Message----- > From: Davanum Srinivas [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 14, 2006 11:00 AM > To: axis-user@ws.apache.org > Subject: Re: Axis 1.* to Axis2 Migration Question > > Please see http://ws.apache.org/axis2/1_1/quickstartguide.html#axiom > > public OMElement nameOfMethod(OMElement element) > > thanks, > dims > > On 12/14/06, Ted Jones <[EMAIL PROTECTED]> wrote: > > To be more specific as to what Axis 1.3 logic I am trying to > > convert, the java:msg provider in Axis 1.3 specifies that the > > service class contains the following method signature (among others): > > > > public void nameOfMethod(org.apache.axis.message.SOAPEnvelope req, > > org.apache.axis.message.SOAPEnvelope resp) > > throws Exception { ... } > > > > This has worked well for us by allowing us to interrogate the > > request, > > > execute our business logic, and return the results in the SOAP > response. > > > > > > Is there an equivalent solution in Axis2? > > > > TIA, > > Ted > > -----Original Message----- > > From: Ted Jones [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, December 13, 2006 3:09 PM > > To: axis-user@ws.apache.org > > Subject: RE: Axis 1.* to Axis2 Migration Question > > > > So, after looking through the documentation, is it accurate to say > > that there is no parallel Axis2 form of a service that uses a > > message provider and will default to an method based on it's > > signature? Does the operation need to be specified now? > > > > Thanks > > > > -----Original Message----- > > From: robert lazarski [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, December 13, 2006 2:42 PM > > To: axis-user@ws.apache.org > > Subject: Re: Axis 1.* to Axis2 Migration Question > > > > This is a good place to start: > > > > http://ws.apache.org/axis2/1_1/migration.html > > > > HTH, > > Robert > > > > On 12/13/06, Ted Jones <[EMAIL PROTECTED]> wrote: > > > > > > > > > I have a web service in Axis 1.3 that is defined using the > > > following > > > > deployment descriptor: > > > > > > <service name="myservice" provider="java:MSG"> > > > > > > > > > <parameter name="allowedMethods" value="executeMyService"/> > > > > > > <parameter name="className" > > > value="com.soap.service.MyWebService"/> > > > > > > </service> > > > > > > The method (executeMyService) accepts the soap request and > > > response envelopes as arguments. What is the parallel > > > implementation for > Axis2? > > > > > > > > > > > > TIA, > > > > > > Ted Jones > > > > > > > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service > Developers) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
