attn dims please : RE: Axis 1.1 vs Axis 1.2rc3 and derived types
dims, It seems that this issue doesn't relate only to derived types, but to the beanMapping as supplied by the server-config.wsdd... In axis 1.1, axis would write out all the objects mapped in the server-config.wsdd... for instance, if you had this in your server-config.wsdd: service name=TestAxis provider=java:RPC parameter name=allowedMethods value=* / parameter name=className value=test.TestObj / beanMapping qname=myNS:Test1 xmlns:myNS=myns:Test1 languageSpecificType=java:test.Test1 / beanMapping qname=myNS:Test2 xmlns:myNS=myns:Test2 languageSpecificType=java:test.Test2/ /service the output wsdl would write a type for both the Test1 and Test2 objects... in Axis 1.2rc3, this is no longer true. Is this expected behavior? Thanks, -Clint -Original Message- From: Dovholuk, Clint [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 26, 2005 4:22 PM To: axis-user@ws.apache.org Subject: RE: Axis 1.1 vs Axis 1.2rc3 and derived types thanks dims, bug 1955 created : http://issues.apache.org/jira/browse/AXIS-1955 -clint (posted to the mailing list in case anyone else wants to view) -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 26, 2005 3:26 PM To: axis-user@ws.apache.org Subject: Re: Axis 1.1 vs Axis 1.2rc3 and derived types this is definitely looks like a bug. do you have a stripped down test case that can be used to recreate the bug? (please open a bug report) thanks, dims On 4/26/05, Dovholuk, Clint [EMAIL PROTECTED] wrote: Hello all, We are trying to switch to Axis 1.2rc3 in order to move to J2SE 5.0 (unless there's another workaround for the package enum that I didn't find?). I have a web service which uses abstract classes/types but when I switched to the axis 1.2rc3 jars, all of a sudden the wsdl that axis creates is no longer representing many (mostly all) of the derived classes... The abstract classes are still created but the classes derived from the abstract class no longer get written to the wsdl... If I expose another method to axis (via server-config.wsdd) in the same class which uses the base type, only THEN will the derived types get written to the wsdl properly... I've searched through the mailing lists to the best of my ability but I can't find this exact issue. Could anybody point me in the right direction or has anybody seen similar issues? I can provide some simple sample classes if people wish but every time I post a 'lengthy' message, I get no replies... :) Thanks, -Clint -- Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Axis 1.1 vs Axis 1.2rc3 and derived types
this is definitely looks like a bug. do you have a stripped down test case that can be used to recreate the bug? (please open a bug report) thanks, dims On 4/26/05, Dovholuk, Clint [EMAIL PROTECTED] wrote: Hello all, We are trying to switch to Axis 1.2rc3 in order to move to J2SE 5.0 (unless there's another workaround for the package enum that I didn't find?). I have a web service which uses abstract classes/types but when I switched to the axis 1.2rc3 jars, all of a sudden the wsdl that axis creates is no longer representing many (mostly all) of the derived classes... The abstract classes are still created but the classes derived from the abstract class no longer get written to the wsdl... If I expose another method to axis (via server-config.wsdd) in the same class which uses the base type, only THEN will the derived types get written to the wsdl properly... I've searched through the mailing lists to the best of my ability but I can't find this exact issue. Could anybody point me in the right direction or has anybody seen similar issues? I can provide some simple sample classes if people wish but every time I post a 'lengthy' message, I get no replies... :) Thanks, -Clint -- Davanum Srinivas - http://webservices.apache.org/~dims/
RE: Axis 1.1 vs Axis 1.2rc3 and derived types
thanks dims, bug 1955 created : http://issues.apache.org/jira/browse/AXIS-1955 -clint (posted to the mailing list in case anyone else wants to view) -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 26, 2005 3:26 PM To: axis-user@ws.apache.org Subject: Re: Axis 1.1 vs Axis 1.2rc3 and derived types this is definitely looks like a bug. do you have a stripped down test case that can be used to recreate the bug? (please open a bug report) thanks, dims On 4/26/05, Dovholuk, Clint [EMAIL PROTECTED] wrote: Hello all, We are trying to switch to Axis 1.2rc3 in order to move to J2SE 5.0 (unless there's another workaround for the package enum that I didn't find?). I have a web service which uses abstract classes/types but when I switched to the axis 1.2rc3 jars, all of a sudden the wsdl that axis creates is no longer representing many (mostly all) of the derived classes... The abstract classes are still created but the classes derived from the abstract class no longer get written to the wsdl... If I expose another method to axis (via server-config.wsdd) in the same class which uses the base type, only THEN will the derived types get written to the wsdl properly... I've searched through the mailing lists to the best of my ability but I can't find this exact issue. Could anybody point me in the right direction or has anybody seen similar issues? I can provide some simple sample classes if people wish but every time I post a 'lengthy' message, I get no replies... :) Thanks, -Clint -- Davanum Srinivas - http://webservices.apache.org/~dims/
