The taskdef is described here:
http://java.sun.com/webservices/docs/1.3/jaxb/ant.html. It looks like
this:
<taskdef name="xjc" classname="com.sun.tools.xjc.XJCTask">
<classpath>
<fileset dir="../../lib" includes="*.jar" excludes="ant.jar"/>
<fileset dir="../../..">
<include name="jaxp/**/*.jar"/>
<include name="jwsdp-shared/lib/**/*.jar"/>
</fileset>
</classpath>
</taskdef>
Ah, I see that we *are* using antcall in some of our xjc invokes (and
some we just invoke it directly). I'll have a look at using macrodef
instead.
Thanks,
Lee
> -----Original Message-----
> From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 03, 2004 6:23 AM
> To: [EMAIL PROTECTED]
> Subject: Re: OutOfMemory and bug #8689
>
> On Thu, 3 Jun 2004, Lee Breisacher <[EMAIL PROTECTED]> wrote:
>
> > So, if you can tell me a different way to invoke the XJC task that
> > doesn't leak classes, or if there is something the JAXB
> developers can
> > do in their implementation/declaration of the XJC task,
> that would be
> > great.
>
> How does your taskdef look and how do you invoke the task 14 times?
> Are these 14 straight tasks or are they invoked via ant(call)?
>
> I'll look into the task implementation, if I can find it.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED] For
> additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
