axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gene Chuang <>
Subject Re: axis ant task in netbeans
Date Thu, 02 Jan 2003 22:28:28 GMT

Thanks for all your valuable input Steve.
>Well, ant does its thing differently; you can't really align the codebase that well
Given that axis standalone commandlines (WSDL2Java, Java2WSDL and Admin) are more stable and
better supported than their ant-task counterparts, would it be simply better (or possible)
for me to write <target>'s that invoke <exec> of the former java programs rather
than trying to run the axis ant-tasks?
 Steve Loughran <> wrote:
----- Original Message -----
From: "Gene Chuang" 
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(
> at java.util.HashMap.get(
> at java.util.Collections$SynchronizedMap.get(
> at
> at
> at
> at
> ...
> 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.

View raw message