I will try in the feature but I suspect you are correct in that it won't have an effect with the SS. The interesting fact is that
when I have a TransformerException that is thrown from Xalan, not
from my Extension Element, I get full SourceLocator info. When I
throw the Exception from my Extension Element, I get the filename
but not the line number info. The problem is probably how I am passing in the SourceLocater into the TransformerException, and
I haven't been able to find any example illustrating how.
I use the SourceLocator to support Markers in Eclipse so when an error shows up in a view, if you click on it it pops open the file and goes to the correct line/column. Kind of handy compared to a stack dump... :-)
Thanks -JG
Storing locators for source documents burns additional storage; Xalan-J doesn't do so unless you request it (http://xml.apache.org/xalan-j/features.html#source_location). Having said that... I'm not sure that switch actually has any effect for stylesheet documents; I'd have to dig into the code and/or try it.
For what it's worth: In my experience, most of the things people want to use line/column information for -- with the possible exception of driving a GUI -- are better addressed by generating an XPath to that point in the document. "Line 5, column 25" is almost meaningless for humans; "/customer/address" has some chance of being directly informative. ______________________________________ Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more. "The world changed profoundly and unpredictably the day Tim Berners Lee got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
