James Strachan wrote:
>
> 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).
What does "not support JAXP 1.1" mean? Does it mean that it can not work
with Xalan2? There is no overlap between Xalan2 and JAXP 1.0.
> So this backwards tag, which uses the old xalan API to do XSLT was added
> specifically for this issue.
>
> Whats the best way forward?
Normally, I would suggest something like the following:
<available property="xalan1.present"
classname="org.apache.xalan.xslt.XSLTProcessorFactory"
classpathref="classpath" />
And then in the javac task:
<exclude name="**/XalanStyleTag.java" unless="xalan1.present" />
Unfortunately, I see that this logic has been factored out of the build.xml
for individual taglibs.
- Sam Ruby
