Re: Warnings for XSLT

2006-05-28 Thread Kamal Bhatt
WARN (2006-05-26) 17:27.19:443 [sitemap.transformer.xslt] (/apps/ccn/exp/query?max=10&city=LON) TP-Processor14/TraxErrorListener: file:/data/content/tsg/ccn/xslt/combine_supub_custom.xsl:65:36 Not too helpful. As I said I fixed it, so I am not bothered by it too much, but I would like to kn

Re: Warnings for XSLT

2006-05-28 Thread Jason Johnston
Kamal Bhatt wrote: Sorry, but this was a cocoon specific issue. The script was working fine as it was. The problem (which got lost thanks to my bad copying and pasting) was not the script, it was with the unexplained warnings (TraxErrorListener) that I got from running the scripts. Is that a

Re: Warnings for XSLT

2006-05-28 Thread Kamal Bhatt
Sorry, but this was a cocoon specific issue. The script was working fine as it was. The problem (which got lost thanks to my bad copying and pasting) was not the script, it was with the unexplained warnings (TraxErrorListener) that I got from running the scripts. Is that a bug or is it someth

Re: Warnings for XSLT

2006-05-28 Thread Jason Johnston
Kamal Bhatt wrote: Apologies, I did not see that. Yes, you are right most of those * is not meant to be there. It was rendering right when I pasted it in. I did not realise that is what the browser does. Sorry people, please ignore the unnecessary *. Someone at work worked out that you don't

Re: Warnings for XSLT

2006-05-28 Thread Martynas Jusevicius
Have you tried ? Martynas On 5/29/06, Kamal Bhatt <[EMAIL PROTECTED]> wrote: Apologies, I did not see that. Yes, you are right most of those * is not meant to be there. It was rendering right when I pasted it in. I did not realise that is what the browser does. Sorry people, please ignore the

Re: Warnings for XSLT

2006-05-28 Thread Kamal Bhatt
Apologies, I did not see that. Yes, you are right most of those * is not meant to be there. It was rendering right when I pasted it in. I did not realise that is what the browser does. Sorry people, please ignore the unnecessary *. Someone at work worked out that you don't need the node() and

Re: Warnings for XSLT

2006-05-26 Thread Lars Huttar
Kamal Bhatt wrote: Hi I keep getting warnings about TraxErrorListener for line 55 and 64 for the XSLT included at the end of this file. To make life easier the problem is with the following lines: and || without the curly braces it does not work, but with them I get the warnings. As the

RE: Warnings for XSLT

2006-05-26 Thread Martijn C. Vos
Ard Schrijvers wrote: > > * == node() (more or less, there are subtle diffs I thought, > but has been to long to remember them) I think * matches only elements, while node() also matches text nodes. * doesn't match attributes, @* does. Not sure about node(). > So I suggest you get rid of a

RE: Warnings for XSLT

2006-05-26 Thread Ard Schrijvers
I have never seen anything like , using { within an xsl namespace element. *{name()}* is unreadible for me, though i have quite some years experience in xslt. So either you are doing something highly complex to achieve something complex, which is good, or you are doing something highly complex