Hi Guys
> Gump does not use the jars checked into CVS. Instead, it uses the latest
> versions of the respective dependencies. In the case where there is a
> major version (Xerces 1&2, Xalan 1&2, Tomcat 3&4), I will generally build
> both for a period of time.
>
> For Xalan 1, that period is over.
>
> If you wish to reproduce this failure, simply specify
> -Dbuild.sysclasspath=only on your invocation of ant.
>
> IMHO, intentionally staying downstream in your dependencies does a
> significant disservice to the Jakarta and xml.apache.org communities.
Firstly most of the XTags library has all gone JAXP 1.1 so there's mostly no
direct dependency on Xalan at all....
This compile error thats being generated is due to a single tag, called
<xalanStyle> which was specifically added for backwards compatability. JAXP
1.1 still doesn't work in some J2EE containers which are hardwired for
JAXP1.0. (When I wrote the tag, WL 6.0 still did not support JAXP 1.1. I've
not had chance to verify WL 6.1 had resolved this issue).
So this backwards tag, which uses the old xalan API to do XSLT was added
specifically for this issue.
I'll happily remove it at some point, when we can be sure servlet engines
can work with JAXP1.1 and this backwards compatability is no longer
required.
Sam, have you any idea when all J2EE containers will support JAXP1.1?
Whats the best way forward?
James
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
