Hi Venkat, After posting the problem, I did use -W flag and everything worked fine. But it created extra classes for request parameters. Anyway thanks for your reply. If you find a way of doing without -W flag, please let me know.
Thanks again!! -Himmat -----Original Message----- From: Venkat Reddy (JIRA) [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 08, 2005 12:11 AM To: Dhange, Himmatsinh Subject: [jira] Commented: (AXIS-2247) WSDL2Java fails to create correct proxy code for web methods with too many parameters. [ http://issues.apache.org/jira/browse/AXIS-2247?page=comments#action_1235 7008 ] Venkat Reddy commented on AXIS-2247: ------------------------------------ Can you please post complete WSDL? Did you use -W flag whie running WSDL2Java? -venkat > WSDL2Java fails to create correct proxy code for web methods with too many parameters. > ------------------------------------------------------------------------ -------------- > > Key: AXIS-2247 > URL: http://issues.apache.org/jira/browse/AXIS-2247 > Project: Apache Axis > Type: Bug > Components: WSDL processing > Versions: 1.2.1, 1.2 > Environment: Windows 2000 amd 2003 server > Axis 1.2 and 1.2.1 > Reporter: Himmat Dhange > > Below is the request schema for which WSDL2Java does not create the > correct porxy code <xsd:element name="PerformUserRegistration"> > <xsd:complexType> > <xsd:all> > <xsd:element name="accountID" type="AccountID"/> > <xsd:element name="accountPassword" type="Password"/> > <xsd:element name="title" type="Title" minOccurs="0"/> > <xsd:element name="firstName" type="FirstName"/> > <xsd:element name="lastName" type="LastName"/> > <xsd:element name="suffix" type="Suffix" minOccurs="0"/> > <xsd:element name="jobTitle" type="JobTitle" minOccurs="0"/> > <xsd:element name="departmentCategory" type="DepartmentCategory"/> > <xsd:element name="departmentDescription" type="DepartmentDescription" minOccurs="0"/> > <xsd:element name="companyName" type="CompanyName" minOccurs="0"/> > <xsd:element name="industryCode" type="RegistrationIndustryCode" minOccurs="0"/> > <xsd:element name="address1" type="StreetAddress"/> > <xsd:element name="address2" type="StreetAddress" minOccurs="0"/> > <xsd:element name="city" type="City"/> > <xsd:element name="wardNameOrProvince" type="WardNameOrProvince" minOccurs="0"/> > <xsd:element name="countryCode" type="CountryCode"/> > <xsd:element name="stateOrProvinceOrRegion" type="StateOrProvinceOrRegion"/> > <xsd:element name="zipOrPostalCode" type="ZipOrPostalCode"/> > <xsd:element name="telephoneCountryCode" type="TelephoneCountryCode" minOccurs="0"/> > <xsd:element name="telephone" type="Telephone"/> > <xsd:element name="faxCountryCode" type="FaxCountryCode" minOccurs="0"/> > <xsd:element name="fax" type="Fax" minOccurs="0"/> > <xsd:element name="emailAddress" type="EmailAddress"/> > <xsd:element name="excludeFromMailings" type="xsd:boolean" minOccurs="0"/> > <xsd:element name="dnbFlag" type="xsd:boolean" minOccurs="0"/> > <xsd:element name="thirdPartyID" type="ThirdPartyID" minOccurs="0"/> > <xsd:element name="password" type="Password"/> > <xsd:element name="userID" type="UserID"/> > <xsd:element name="securityWord" type="SecurityWord" minOccurs="0"/> > </xsd:all> > </xsd:complexType> > </xsd:element> > Axis 1.2.1 normally adds all request elements as method argument, but for this request (which has 30 elements) it adds an argument of type PerformUserRegistration as follows: > public PerformUserRegistrationResponse performUserRegistration(PerformUserRegistration parameters) throws java.rmi.RemoteException, objects.v3_0.developer.factiva.FaultException; > But this method signature gives compilation error because class PerformUserRegistration does not get generated in proxy code. > Same request works fine in Axis 1.1 and creates method with 30 arguments. > Is this a bug in Axis 1.2.0 and 1.2.1? Is there a way around to resolve this issue? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
