> 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?
You try use JAXP1.1 to do an XSLT transform and you get an Exception thrown
when running inside WebLogic 6.0. If you're interested in the details,
www.bea.com has a bunch of support requests about it.
> Does it mean that it can not work
> with Xalan2?
I think so - I'll try confirm.
> There is no overlap between Xalan2 and JAXP 1.0.
I know. But there is overlap between JAXP1.0 and JAXP1.1. So its a JAXP
issue not Xalan per se.
> > 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.
Thanks Sam.
Not compiling the file is the easy part - its what to do with the TLD and
documentation if I put that in - thats what I'm scratching my head over.
I'll try add something like that to fix the problem - though it is hard to
test, not being able to run a GUMP build so it could take a few days (and
GUMP emails) to fix it.
I'm actually tempted to move the offending code to a contrib area and not
use it by default and have a special build target that would build a version
of XTags for use in old containers. I'll think some more a little on the
matter and try fix it by Monday / Tuesday.
James
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
