----- Original Message -----
From: "Alan Moore" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 21, 2002 9:38 AM
Subject: RE: WSDL2JAVA problem
> I didn't use the ant <apply> task but instead used the <java> task. It has
a
> fork option that I found was required in order to get things to work
> properly (someone else might be able to explain why...)
probably because <java> with fork=false cant handle System.exit() calls. I
know you will say 'use a security manager, then', to which I must add 'what,
and break a large percentage of existing builds'
in my experience, the time hit is neglible, and it frees you from static
resource consumption.
>
> Here is my WSDL2Java build steps (one for server-side, one for the
client):
>
> <!-- generate axis client .java files -->
> <java classname="org.apache.axis.wsdl.WSDL2Java"
> classpath="${axis.classpath}" fork="true">
> <arg line="-p packagename"/>
> <arg value="-o"/> <!-- -o path follows -->
> <arg path="${g4-src.src}"/>
> <arg path="${g4-wsdl.src}/das.wsdl"/>
> </java>
> <!-- generate axis server .java files -->
> <java classname="org.apache.axis.wsdl.WSDL2Java"
> classpath="${axis.classpath}" fork="true">
> <arg line="--server-side --skeletonDeploy true -p packagename"/>
> <arg value="-o"/> <!-- -o path follows -->
> <arg path="${g4-src.src}"/>
> <arg path="${g4-wsdl.src}/dasEv.wsdl"/>
> </java>
>
> I saw a mention of a <WSDL2Java> task but haven't looked into it yet. You
> might want to investigate that as well.
It is in the test directory. I have some (unapplied) patches to make it more
robust, but you will probably need the axis libs in your ant classpath.
