----- Original Message ----- From: "Gene Chuang" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 02, 2003 11:00 Subject: Re: axis ant task in netbeans
> > >I'd try specifiying an output="some file name" attr > Yup, that did the trick, at least when running the task in NetBeans. The wsdl was generated after the "BUILD SUCCESSFUL" message, although subsequently NB pops an Exception window with a StackOverflow message: > Annotation: Exception occurred in Request Processor > java.lang.StackOverflowError > at java.util.HashMap.hash(HashMap.java:257) > at java.util.HashMap.get(HashMap.java:313) > at java.util.Collections$SynchronizedMap.get(Collections.java:1938) > at org.apache.tools.ant.module.api.lIntrospectedInfo.isKnown(IntrospectedInfo.j ava:244) > at org.apache.tools.ant.module.api.lIntrospectedInfo.analyze(IntrospectedInfo.j ava:386) > at org.apache.tools.ant.module.api.lIntrospectedInfo.analyze(IntrospectedInfo.j ava:452) > at org.apache.tools.ant.module.api.lIntrospectedInfo.analyze(IntrospectedInfo.j ava:452) > ... > Oh well, I got the wsdl finally from the Ant, so I'm not gonna worry too much about this. However, with the output="file" attr, running Ant from commandline still gets me the WSDLException faultCode=PARSER_ERROR. I'm not sure why the two runs are going through different codepaths, unless this is still a classpath issue... Its probably attributable to XML parsers. > I'm also surprised that the the standalone Java2WSDL and ant-task Java2Wsdl do not use the same code for >attribute processing; this accounts for the majority of the stumbling blocks I'm going through, having to plug in >default values that I assume will be supplied to me. Well, ant does its thing differently; you cant really align the codebase that well. >Hopefully this will change in the next release? no, though we have patched that extraClasses NPE you discovered.
