Hi Ganesh,
This did not give the error and resulted in expected results. I
could get the result with JRE itself i.e., without having to specify
the -Xbootclasspath/p flag. Does that mean XalanJ 2.4.1, Saxon
6.5.3, MSXML3, etc are suppressing this error? Whether the
processors which issue this error are XSLT compliant or is it the
otherway?
It's one of the many "recoverable errors" in XSLT. Compliant
processors can signal the error (and halt) or ignore the attribute
(and carry on); some processors will give you a warning if they do the
latter and others won't. So unfortunately there's a large range of
compliant behaviour.
Cheers,
Jeni
---
Jeni Tennison
http://www.jenitennison.com/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list