You might get better reports by using XSL's own import/include functions rather than preprocessing with XInclude. (Haven't tried it recently so I'm not certain.)
______________________________________ "You build world of steel and stone I build worlds of words alone Skilled tradespeople, long years taught: You shape matter; I shape thought." (http://www.songworm.com/lyrics/songworm-parody/ShapesofShadow.html) From: Adrian Herscu <adrian.her...@gmail.com> To: xalan-j-users@xml.apache.org Date: 07/07/2011 03:19 AM Subject: using xalan line number function with xinclude Hi all, I am building a testing framework for my company using Xalan-based XSL with Java backend. In one of my XSL sheets I am using the nodeinfo:line-number() function supplied by Xalan to track line numbers of elements in the input document to elements in a generated report document. Everything worked fine until the input document got too large to be easily manageable. Then, I decided to extract sections of it into subdocuments and reference those by xinclude elements. Now the nodeinfo:line-number() function returns the line number of xinclude element instead of the line number in the referenced document. Obviously not what I looked for... Please help, Adrian. P.S. Also posted on http://stackoverflow.com/questions/6585985/using-xalan-line-number-function-with-xinclude
