I would like TextPad to catch Xalan error messages for XSL transformations started from the editor and to jump directly to the error in the source.
I did setup a new tool menu entry and it starts Xalan transformations without trouble. I used the following parameters:
Regular expression: ^file:///\([^;]+\)\; Line \([0-9]+\)\; Column \([0-9]+\)
Options Set: Capture Output
File register=1, Line register=2, Column register=3
The regular expression matches if I try it manually. But TextPad does not jump to the error in case of an erroneous transformation. However, TextPad seems to distinguish between successful and erroneous transformations, as it reports "Bonne exécution du processus" at the end of the result window if the transformation went well, or "Processus terminé avec code quitter -1" if it did not.
What am I doing wrong? Any help would be welcome!
I am using the french version of TextPad 4.5.0.
Olivier
Here is a sample Xalan output in case of an unsuccessful transformation:
java org.apache.xalan.xslt.Process -diag
-in build\hei-csched-2002-summer.xpg.xml
-xsl transform\xpage\xpg2fo.xsl
-out build\hei-csched-2002-summer.xfo.xml
file:///F:/work/olivier/prof/projets/hei/hei-xml/xpg/build/hei-csched-2002-summer.xpg.xml; Line 5; Column 12; XSLT Error (javax.xml.transform.TransformerException): The prefix "dcx" for element "dcx:title" is not bound.
Processus terminé avec code quitter -1
How to capture Xalan command-line error messages from TextPa
Moderators: AmigoJack, bbadmin, helios, Bob Hansen, MudGuard
-
Olivier Lange
Re: How to capture Xalan command-line error messages from Te
Well by a 'click' of good fortune I found the answer...
One just needs to double-click on the error message in TextPad's result window to jump to the source file containing the error!
Sorry for the question, I missed this in the documentation and thought TextPad would jump automatically to the source error.
Hopefully might the above settings be useful to other XSL developpers, as they work perfectly well. I'll see if this thread can be converted to a TextPad tip.
Kind regards
Olivier
One just needs to double-click on the error message in TextPad's result window to jump to the source file containing the error!
Sorry for the question, I missed this in the documentation and thought TextPad would jump automatically to the source error.
Hopefully might the above settings be useful to other XSL developpers, as they work perfectly well. I'll see if this thread can be converted to a TextPad tip.
Kind regards
Olivier