How to avoid <xsl:message > instruction prints stylesheet file informations ?

Subjects

•	Home
•	Xalan extension functions
•	Fomatting question serializing DOM with pretty print
•	xalan with pull parser
•	Cannot find the declaration
•	Apache Xalan drop support to run on JRE 1 1 x
•	Why does Doctype change processing of a document
•	Node set to XML string via Java extensions in Xalan J: possible?
•	Templates/Transformers + thread safety???
•	Problem evaluating xpath with muliple prefix with different namespace
•	remove an arbitrary attribute from xsl output
•	Xalan3 XSLT 2 0 XPath 2 0 support?
•	Problem using compiled translets with Xalan !!
•	Xalan and jstl 1 1 problem with transform tag
•	NullPointer in DOM2DTM getLocalName
•	URIResolvers base parameter with xsltc and cascaded imports
•	Performance problem for Xalan J on intel dual core
•	Standard libraries in JAXP?
•	Serializing a DOM tree to XML file, customize entities replacement
•	Library Conflict Involving BCEL Library
•	A question on how users are using <xsl:message >
•	Kevin Cormier as a new Apache Xalan J committer
•	Struggling to iterate over tokenized string
•	Xalan count() trouble
•	Problem with recursive xpath
•	Error when switching to java 1 5
•	document( ' ')
•	Problem with Xalan2 7 0 transformation
•	cr/lf options
•	entity encoded XML
•	can xalan transform 2 xml using one xslt?
•	Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
•	xsl transform with cdata section elements
•	xslt parameters not expanded
•	Weird behavior of XPath evaluate()
•	How to avoid <xsl:message > instruction prints stylesheet file informations ?
•	Cannot find SimpleTransform subdirectory after installing Xalan J
•	recover from document not found exceptions
•	jdk1 5 and Xalan jar differences?
•	Performance Issue
•	Error/Bug adding floating point numbers
•	XPathAPI: eval exp using nodes with default namespace
•	modifying xalan to output invalid XML
•	NullPointerException
•	mege two separate xml nodes into one
•	Is this a XALAN document identification bug?
•	is StylesheetRoot really java io Serializable ?
•	transform() fails for DOMSource but succeeds for StreamSource
•	Thoughts on Transformer parameter passing
•	HELP, Xalan and jstl 1 1 problem with transformer
•	Problem with XPath namespace axis?
•	string utils:replace deleting search string if replacement string is an HTML
•	help with enumeration values pls
•	xalan 2 5 1 vs 2 7 performance question
•	How to insert/update in XML document
•	HTML Serialization and Handling of Ampersands in HREF Attributes
•	XHTML link tag stripping
•	SystemId Unknown; Line #24; Column #49; java lang NullPointerException
•	xpath text() help
•	Apostrophe problem with xalan 2 7 0
•	How to set variables in XML document?

Links

Home

Oracle database error code ...

How to avoid <xsl:message > instruction prints stylesheet file informations ?

How to avoid <xsl:message > instruction prints stylesheet file informations ?

2006-10-30 - By Erin Harris

Reply: 1 2 3 4

Hi André,

You could write your own error listener such as the following:

public class MyErrorListener implements ErrorListener {
public void warning(TransformerException exception) throws
TransformerException {
System.err.println(exception.getMessage());
}

public void error(TransformerException exception) throws
TransformerException {
System.err.println(exception.getMessageAndLocation());
}

public void fatalError(TransformerException exception)
throws TransformerException {
System.err.println(exception.getMessageAndLocation());
}
}

To set the error listener on the transformer use the method:
Transformer.setErrorListener(ErrorListener)

Thanks.

Erin Harris

André Mercadier <andre.mercadier@(protected)>
28/10/2006 04:22 AM

To
<xalan-j-users@(protected)>
cc

Subject
How to avoid <xsl:message> instruction prints stylesheet file informations
?

Hello,

I'm using Xalan 2.7.0 with Xerces 2.7.1 on a MS-DOS environment with the
command line utility to perform XSLT transformations (java
org.apache.xalan.xslt.Process -IN foo.xml -XSL foo.xsl -OUT foo.out -PARAM
param value).

My foo.xsl stylesheet contains several <xsl:message>STEP xxx</xsl:message>
to trace the steps it reaches, but the printed message is not only "STEP
xxx" but :

"file:///c:/my_very_complex_directory/foo.xsl ; Line x; Column y; STEP xxx
".

Is it possible to avoid the stylesheet file informations (which don't
interest users), keeping only the message in the <xsl:message> tag ?

Thanks a lot.

<br><font size=2 face="sans-serif">Hi André,</font>
<br>
<br><font size=2 face="sans-serif">You could write your own error listener
such as the following:</font>
<br>
<br><font size=2 face="Courier">        public
class MyErrorListener implements ErrorListener {</font>
<br><font size=2 face="Courier">         
      public void warning(TransformerException exception)
throws TransformerException {</font>
<br><font size=2 face="Courier">           
            System.err.println(exception
.getMessage());</font>
<br><font size=2 face="Courier">         
      }</font>
<br>
<br><font size=2 face="Courier">         
      public void error(TransformerException exception)
throws TransformerException {</font>
<br><font size=2 face="Courier">           
            System.err.println(exception
.getMessageAndLocation());</font>
<br><font size=2 face="Courier">         
      }</font>
<br>
<br><font size=2 face="Courier">         
      public void fatalError(TransformerException
exception) throws TransformerException {</font>
<br><font size=2 face="Courier">           
            System.err.println(exception
.getMessageAndLocation());</font>
<br><font size=2 face="Courier">         
      }</font>
<br><font size=2 face="Courier">        }</font>
<br>
<br><font size=2 face="sans-serif">To set the error listener on the transformer
use the method: </font><font size=2 face="Courier">Transformer.setErrorListener
(ErrorListener)</font>
<br>
<br><font size=2 face="sans-serif">Thanks.<br>
<br>
Erin Harris<br>
<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>André Mercadier <andre
.mercadier@(protected)></b>
</font>
<p><font size=1 face="sans-serif">28/10/2006 04:22 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif"><xalan-j-users@(protected)></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">How to avoid <xsl:message> instruction
prints stylesheet file informations ?</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2 face="Arial">Hello,</font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">I'm using Xalan 2.7.0 with Xerces 2.7.1 on
a MS-DOS environment with the command line utility to perform XSLT
transformations
(java org.apache.xalan.xslt.Process -IN foo.xml -XSL foo.xsl -OUT foo.out
-PARAM param value).</font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">My foo.xsl stylesheet contains several <xsl
:message>STEP
xxx</xsl:message> to trace the steps it reaches, but the printed
message is not only "STEP xxx" but :</font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">"</font><a href="file:///c:/my_very_complex
_directory/foo.xsl%20;%20Line%20x;%20Column%20y;%20STEP%20xxx" target=_blank>
<font size=2 face="Arial"><u>file:///c:/my_very_complex_directory/foo.xsl
; Line x; Column y; STEP xxx</u></font></a><font size=2 face="Arial">".<
/font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">Is it possible to avoid the stylesheet file
informations (which don't interest users), keeping only the message in
the <xsl:message> tag ?</font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">Thanks a lot.</font>
<br>