You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2001/03/18 07:33:39 UTC
[Bug 1009] New - Malformed attribute expression lacks line/column information
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1009
*** shadow/1009 Sat Mar 17 22:33:38 2001
--- shadow/1009.tmp.29911 Sat Mar 17 22:33:38 2001
***************
*** 0 ****
--- 1,37 ----
+ +============================================================================+
+ | Malformed attribute expression lacks line/column information |
+ +----------------------------------------------------------------------------+
+ | Bug #: 1009 Product: XalanJ2 |
+ | Status: NEW Version: 2.0.0 |
+ | Resolution: Platform: PC |
+ | Severity: Major OS/Version: Windows NT/2K |
+ | Priority: Medium Component: Xalan |
+ +----------------------------------------------------------------------------+
+ | Assigned To: xalan-dev@xml.apache.org |
+ | Reported By: bevan.arps@clear.net.nz |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ While developing a template I encountered this error:
+
+ ========= Parsing file:C:/Dev/XSLT/XSLTdoc/XSLTdoc.run.xsl ==========
+ XSL Error: Could not parse file:C:/Dev/XSLT/XSLTdoc/XSLTdoc.run.xsl document!
+ XSL Error: processStylesheet not successful!
+ XSLT: XercesLiaison.parse error
+ Xalan: was not successful.
+ XSLProcessor: done
+
+ I eventually traced the line causing the fault to this:
+
+ <link ref="{generate-id($template)"><xsl:value-of select="$caption"/></link>
+
+ The attribute expression for the ref attribute lacks the closing "}" - adding
+ this character fixed the stylesheet.
+
+ The bug is that the error messages did not detail the line/column for where the
+ parse failure occurred - in my case I had a 14K stylesheet to troll through by
+ hand.
+
+ I reproduced the same behaviour in both 1.2.2 and 2.0.0.
Re: debugging style sheets
Posted by Phil Friedman <pf...@terralink.com>.
And when you find the better way, please share it! My style sheet
development would go much faster if Xalan-J included stylesheet line
numbers in all messages.
Regards, Philip Friedman -- Terralink Software Systems -- 207-772-6500 x101
On Mon, 19 Mar 2001 12:06:39 -0800, Joanne Bogart <jr...@SLAC.Stanford.EDU> may have written:
|
|
|bugzilla@apache.org wrote:
|>
|> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1009
|>
|> *** shadow/1009 Sat Mar 17 22:33:38 2001
|> --- shadow/1009.tmp.29911 Sat Mar 17 22:33:38 2001
|> ***************
|> *** 0 ****
|> --- 1,37 ----
|> + +============================================================================+
|> + | Malformed attribute expression lacks line/column information |
|
|I've encountered similar behavior using Xalan-J from the command line;
|that is, syntax errors in my stylesheet yield error messages of greater
|or lesser comprehensibility lacking any line- or column-number information.
|In some cases, at least, it seems that xalan could report this information
|along with the error. If it would be useful, I could try to reproduce
|the things I've seen with a minimal example and submit a bug report.
|
|In the meantime, I'm wondering if there is any better way to debug
|this kind of problem that what I've been doing: commenting out anything
|that seems suspicious to see if the error goes away or changes.
|
|TIA,
| Joanne
|--
|Joanne Bogart jrb@slac.stanford.edu
|SLAC, MS 71 (650) 926-3685 phone
|Stanford University (650) 926-2923 FAX
|P.O. Box 4349
|Stanford, CA 94309
debugging style sheets
Posted by Joanne Bogart <jr...@SLAC.Stanford.EDU>.
bugzilla@apache.org wrote:
>
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1009
>
> *** shadow/1009 Sat Mar 17 22:33:38 2001
> --- shadow/1009.tmp.29911 Sat Mar 17 22:33:38 2001
> ***************
> *** 0 ****
> --- 1,37 ----
> + +============================================================================+
> + | Malformed attribute expression lacks line/column information |
I've encountered similar behavior using Xalan-J from the command line;
that is, syntax errors in my stylesheet yield error messages of greater
or lesser comprehensibility lacking any line- or column-number information.
In some cases, at least, it seems that xalan could report this information
along with the error. If it would be useful, I could try to reproduce
the things I've seen with a minimal example and submit a bug report.
In the meantime, I'm wondering if there is any better way to debug
this kind of problem that what I've been doing: commenting out anything
that seems suspicious to see if the error goes away or changes.
TIA,
Joanne
--
Joanne Bogart jrb@slac.stanford.edu
SLAC, MS 71 (650) 926-3685 phone
Stanford University (650) 926-2923 FAX
P.O. Box 4349
Stanford, CA 94309