Hi Gary,
It seems to me that, the two important XalanJ tests issues that
you've indicated and are remaining to be addressed, are following (and
my thoughts, as well),
On Sun, Jan 29, 2023 at 8:32 PM Gary D. Gregory <ggreg...@apache.org> wrote:
> When I run "build api", I see a lot of:
> [xalantest] line 9 column 1 - Error: <ul-tag> is not recognized!
> [xalantest] line 11 column 1 - Error: <li-tag> is not recognized!
> [xalantest] line 13 column 2 - Error: <li-tag> is not recognized!
I think, these XalanJ tests console verbose results should ideally be
solved (these console messages, should be suppressed, or need to be
produced with more context information). I'm currently not able to
find, any literal string "is not recognized!" anywhere within tests
codebase or tests supporting files, or within XalanJ implementation.
We could, explain facts and our future plans to address this issue,
within XalanJ 2.7.3 release notes. Any thoughts, please?
>
> When I run "build conf.xsltc", I see a lot of:
>
> [xalantest] (Location of error unknown)Message from MESSAGE
I think, error messages like these are ok, to appear on XalanJ tests
console. It seems to me that, these console messages are coming,
because of the use of XalanJ implementation class DefaultErrorHandler
at lot of places within XalanJ tests codebase. These usage within
XalanJ tests codebase is something like following,
Transformer factory = TransformerFactory.newInstance();
factory.setErrorListener(new DefaultErrorHandler());
Templates templates = factory.newTemplates(..);
The XalanJ tests console error message (Location of error unknown),
only seems to occur for XalanJ xsltc tests. For more XalanJ
implementation details about this, we can look at the XalanJ class
org.apache.xml.utils.DefaultErrorHandler (method printLocation(..)),
which has something like following,
if(null != locator)
{
......
}
else
pw.print("("+XMLMessages.createXMLMessage(XMLErrorResources.ER_LOCATION_UNKNOWN,
null)+")");
To solve this, we can perhaps, implement a new XalanJ error handler
within tests codebase. But the usage of code pattern,
factory.setErrorListener(new DefaultErrorHandler()) within XalanJ
tests codebase is very wide-spread, and it'd be lot of work to improve
this.
We could, explain facts and our future plans to address this issue,
within XalanJ 2.7.3 release notes. Any thoughts, please?
As mentioned by others, on another thread of this list, recently, that
XalanJ tests console messages like "PASS! StylesheetTestlet{trax}
output16.xsl" should be suppressed. This shall be lot of work, to
change XalanJ tests codebase to improve upon this. I personally feel
that, these PASS console messages are ok. They seems to give a
feeling, to users running these tests, that lot of good things are
happening while running XalanJ tests amidst few console error
messages.
I could also suggest that, users can run XalanJ tests like as follows
: 'build conf.xsltc > xalanj_tests.conf.xsltc.log' to persist the
tests results within file. This way, console shall be quiet, and users
can look at the produced file to analyze the XalanJ tests output.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
