W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > October 2007

Re: XSLT line numbers, <code>, etc.

From: Roland Gülle <roland@7val.com>
Date: Mon, 8 Oct 2007 15:46:18 +0200
Message-Id: <BAF27719-8366-4C70-B40D-B4187C6F7662@7val.com>
Cc: public-mobileok-checker <public-mobileok-checker@w3.org>
To: Sean Owen <srowen@google.com>

> I don't have any answer for the XSLT line-number issue. The Java
> function only works on a Saxon-built DOM. When I try to have the XSLs
> use the Saxon-built DOM version of the moki document I get some new,
> undecipherable error. So there was not another answer to this? I
> thought there may have been some other way to do this in XSL. I think
> the XSL-based approach is indeed turning out to be more complex than
> imagined, and I don't know if this one is solvable.
I have tested a bit more and have a general problem.
When using a hardcoded:
				<position tidied="false" type="LINE_COLUMN"/>
in in the result document,
I get the exception:

Exception in thread "main" java.lang.NullPointerException
         at org.w3c.mwi.mobileok.basic.TestSubResultPosition.valueOf 
         at org.w3c.mwi.mobileok.basic.TestSubResult.<init> 
         at org.w3c.mwi.mobileok.basic.Tester.runTests(Tester.java:68)
         at org.w3c.mwi.mobileok.basic.Tester.main(Tester.java:145)

I've also tried without column, tidied true, a line number from the  
CSS test, ...
Same result.

Is this a general problem in the Java code or only a problem with  
hardcoded values?

Received on Monday, 8 October 2007 13:46:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:21:19 UTC