I tried with 1.0, too. I will try with -s option to see if the parameter is getting added. Have you tried with my zip contents?
Thanks, Ozzie -----Original Message----- From: Suyog Gandhi [mailto:[EMAIL PROTECTED] Sent: Friday, May 26, 2006 10:44 AM To: axis-user@ws.apache.org Subject: RE: Incorrect parameter type in WSDL2Java generated stub method OMElement instead of specific type I have created the stub in a same way u creating, and it is creating proper stubs for me. But I didn't use -s option. Also I am using WSDL2Java from AXIS2 1.0 release version, not a snapshot. Hoep it helps. Suyog -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, May 26, 2006 9:48 AM To: axis-user@ws.apache.org Subject: RE: Incorrect parameter type in WSDL2Java generated stub method OMElement instead of specific type Has no-one ever run into this problem? This in reference to Axis2. Thanks, Ozzie -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, May 25, 2006 1:32 PM To: axis-user@ws.apache.org Subject: RE: Incorrect parameter type in WSDL2Java generated stub method OMElement instead of specific type The WSDL operation: <wsdl:operation name="Update_MemberPCPDetail"> <soap:operation soapAction="urn:ProviderService"/> <wsdl:input> <soap:header message="tns:Update_MemberPCPDetail_Request" part="context" use="literal"/> <soap:header message="tns:Update_MemberPCPDetail_Request" part="header" use="literal"/> <soap:body parts="request" use="literal"/> </wsdl:input> <wsdl:output> <soap:header message="tns:Update_MemberPCPDetail_Response" part="context" use="literal"/> <soap:body parts="response" use="literal"/> </wsdl:output> <wsdl:fault name="ESBError"> <soap:fault name="ESBError" use="literal"/> </wsdl:fault> </wsdl:operation> The Message definitions: <wsdl:message name="Update_MemberPCPDetail_Request"> <wsdl:part name="context" element="c:Context"/> <wsdl:part name="header" element="h:ESBHeader"/> <wsdl:part name="request" element="m:ProviderService_Update_MemberPCPDetail_Request"/> </wsdl:message> <wsdl:message name="Update_MemberPCPDetail_Response"> <wsdl:part name="context" element="c:Context"/> <wsdl:part name="response" element="m:ProviderService_Update_MemberPCPDetail_Response"/> <wsdl:part name="exception" element="e:ExceptionList"/> </wsdl:message> Why isn't the parameter in the method of type "com.wellpoint.service.provider. ProviderServiceUpdateMemberPCPDetailRequestDocument"???? It is "org.apache.axiom.om.OMElement". What am I doing wrong???? This is a doc/lit. Thanks, Ozzie -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 24, 2006 10:07 AM To: axis-user@ws.apache.org Subject: Incorrect parameter type in WSDL2Java generated stub method OMElement instead of specific type The generated stub source doesn't contain the correct parameter type in the service method. Instead of having the specific type as specified in the WSDL for the parameter, it contains the generic "org.apache.axiom.om.OMElement" type. The stub was generated using Axis2 1.0 WSDL2Java tool. D:\dev\wellpoint\SAF\wsdl\ProviderDomain>d:\devtools\axis2-SNAPSHOT\bin\ WSDL2Java.bat -uri ProviderService_Binding_JMS_V0100.wsdl -s -o codegen -d xmlbeans -p com.wellpoint.integration.saf.int.provider.axis2 /** * Auto generated method signature * @see com.wellpoint.integration.saf.int.provider.axis2.ProviderService#UpdateM emberPCPDetail * @param param0 * @param param1 * @param param2 */ public org.apache.axiom.om.OMElement UpdateMemberPCPDetail( org.apache.axiom.om.OMElement param0,com.wellpoint.esb.context.ContextDocument param1,com.wellpoint.esb.header.ESBHeaderDocument param2) The first parameter should have been "com.wellpoint.service.provider.ProviderUpdateMemberPCPDetailRequestDocu ment". JIRA Issue: http://issues.apache.org/jira/browse/AXIS2-765 Thanks, Ozgur (Ozzie) Gurkan Wellpoint Member 2 - SAF Team This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. --------------------------------------------------------------------- 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] This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
