Return-Path: Delivered-To: apmail-xml-axis-user-archive@xml.apache.org Received: (qmail 94531 invoked by uid 500); 2 Jan 2003 22:28:22 -0000 Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@xml.apache.org Received: (qmail 94518 invoked from network); 2 Jan 2003 22:28:21 -0000 Message-ID: <20030102222828.59327.qmail@web11104.mail.yahoo.com> Date: Thu, 2 Jan 2003 14:28:28 -0800 (PST) From: Gene Chuang Subject: Re: axis ant task in netbeans To: axis-user@xml.apache.org In-Reply-To: <00fe01c2b296$f6a51e10$1219570f@ranier> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1846082601-1041546508=:58254" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N --0-1846082601-1041546508=:58254 Content-Type: text/plain; charset=us-ascii 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 's that invoke of the former java programs rather than trying to run the axis ant-tasks? Steve Loughran wrote: ----- Original Message ----- From: "Gene Chuang" To: 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. --0-1846082601-1041546508=:58254 Content-Type: text/html; charset=us-ascii

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 <steve_l@iseran.com> wrote:


----- Original Message -----
From: "Gene Chuang"
To:
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.
--0-1846082601-1041546508=:58254--