Hi, I have to admit that the WSDL2Java tool has poor error messages. The primary reason for the tool to have hideous error messages is that it does no validation so far. What you can do for now is to use something like the Capeclear SOA editor to validate the WSDL. If the WSDL is valid and the codegen still complains please attach the WSDL (you might need to file a JIRA as well :)). In the meantime we'll try to make the WSDL2java error messages more meaningful.
Ajith On 2/27/06, Tachtevrenidis, Kosta <[EMAIL PROTECTED]> wrote: > > Greg, > > I have gotten that a lot too. What I do to get an idea of what is going on > is to use the wsewsdl3.exe tool to try to generate code for .NET, which have > a pretty good error message capability. Just my thoughts. > > Kosta Tachtevrenidis > http://www.weyer.com/dmg > > > ________________________________ > From: Greg Michalopoulos [mailto:[EMAIL PROTECTED] > Sent: Monday, February 27, 2006 1:49 PM > To: [email protected] > Subject: how to debug Axis2 WSDL2Java > > > > I am getting exceptions when running WSDL2Java in Axis2, is there any way to > get feedback from the application what might be wrong with my WSDL? > > Thanks, > Greg > -- Ajith Ranabahu
