XSLT fn prefix error in external xsl

G'day,

A bit of a mystery bug here. I have a few xsl components being rendered by external stylesheets, some of which use xslt functions from the fn namespace.
(fn:exists, fn:normalize-space)

All of these were working until yesterday. I went to preview the component in sitepub, and got the following error:

Component preview failed. Could not load component XSL into XMLDOM. com.interwoven.livesite.common.xml.ValidationError mColumn[58] mLine[18] mSystemID[null] mPublicID[null] mType[FATAL] mMessage[Prefix must resolve to a namespace: fn]

I don't have the namespace declared in my style sheet, only the default xsl is declared. But this is documented as being valid, if the namespace name matches the prefix, you don't have to explicitly declare the namespace in ur stylesheet.

To get rid of this error in sitepub, I have to explicitly define the fn namespace... however, this was working for weeks before, until yesterday.

Adding the namespace also has caused problems on the runtime server, and am now getting this error in my runtime:

SystemId Unknown; Line #119; Column #67; java.lang.NoSuchMethodException: For extension function, could not find method org.apache.xml.utils.NodeVector.normalizeSpace([ExpressionContext,] ).

I know developers were doing alot of rebuilds yesterday of content center, not sure if libs got messed up or not...

Any ideas?

Find more posts tagged with

Comments

sgouin

Just to offer a bit more context, we're running on TS 7.3.2 .... xslt works fine on the runtime without the explicit fn namespace declaration.

Same xslts fail when previewing the component in sitepub.

Rick Poulin

You don't need to specify the prefix at all on standard XPath 1.0 functions. LiveSite doesn't support XPath 2.0 functions because of the underlying parser it uses. If you DO use the prefix, you should always explicitly declare the namespace. If you had it working some other way, I can't explain what change might've caused it to break all of a sudden...

sgouin

Thanks Rick... i think what may have happened is, I created a simple external stylesheet, referenced it from my component, so I could save it...then modified the stylesheet in my xml editor and added in all of the function calls etc.

I was using the prefix, but without the namespace declaration...but it has worked in runtimes and sitepub page previews.

I suspect I may have not previewed the actual component directly since making the changes to my external xslt.

Possible that there are different parser implementations (or bug) between a component preview and page preview or runtime instance?

Rick Poulin

Possible that there are different parser implementations (or bug) between a component preview and page preview or runtime instance?

There is a difference for sure.. Try outputting an   for example.. I have yet to find a (pure xsl) way that works on both sides (at least, in 7.2.0)