When it comes to 'code first' , you may find the jibx tools superior and they can substitute for the axis2 java2wsdl, while still fitting into axis2. This article sums up the situation:
http://www.infoq.com/articles/sosnoski-code-first I've just spent the last few weeks following that article and while the jibx docs are a bit lacking, searching thru the mailing list archives and the code gave me the answers I was looking for. In general, I've been a skeptic of code first but the tech has finally arrived to make it a viable option, IMHO - particuraly for legacy apps. HTH, Robert On Nov 11, 2007 12:48 PM, Hoda, Nadeem [USA] <[EMAIL PROTECTED]> wrote: > > > > I tried a simple case of inheritance, where I had: > > public class MyBaseVOClass { > ..... > } > > and > > public class MyExtendedVOClass extends MyBaseClass { > > private SomeOtherClass someOtherClass; > > //getters/setters > > } > > Then a service class to implement the above VOs: > > public class MyServiceClass { > > public MyExtendedVOClass myWebMethod(String inputString, > MyExtendedVOClass myExtendedVOClass ) {...} > } > > > I used the samples/quickstart example as a model (code to generated wsdl), > and the WSDL looked fine, but: > > 1. An Axis2 client fails to invoke the service, failing on an unrecognized > type > 2. Eclipse Web Services Explorer divided the results into "Group 1" and > "Group 2" with "Group 1" being erroneous > 3. .NET consumed the service, but failed to return the correct results > (getting the equivalent of the "Group 1" results from eclipse). > > Is this a known issue? i.e., Java to WSDL on inherited types fails or causes > unpredictable results on the client side? > > Thanks, > > Nadeem > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
