----- Original Message ----- From: "R. Lake" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, May 20, 2002 3:17 PM Subject: Re: WSDL2JAVA problem
> This is possibly a similar effect I'm seeing except with Java2WSDL. I've > tried setting the classpath to ".;xerces.jar" to get example 6 of the user > guide working so perhaps there's a conflict between Xerces and JDK1.4? The > other examples must have picked up and used the JDK parser correctly in > order to function but am I correct in observing that the WSDL tools appear > to have an issue with this? Ant does not (currently)[*] propagate any bits of the system classpath down to <java> calls when fork=false except for java.* and javax.* classes. So in java1.4, all the new org.w3c stuff is not accessible till you set forking on. I'd do that anyway, and set failonerror=true just to pick up errors. [*] there is a fix for this, it is on a notebook with a dead motherboard 3 feet away from me but it may make the next ant1.5 beta. Problem is, where do we draw the line between runtime stuff we want to pass down, and other classpath cruft that we dont? -steve
