-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
paths.xsl//tr:target-base-name returns empty string #1
Comments
In all cases that I tested, the tr:content element that was passed to the function had a base attribute. |
Hi Gerrit, test.xpl <p:load> <tr:paths name="paths" pipeline="test.xpl"> <tr:store-debug pipeline-step="test/paths"> I am calling the test.xpl passing in these file and clades options clades="publisher=pearson-it,settore=speciali,book=regondi-strade-maestre" if in cascade/xsl/paths.xsl I use $content/@name <xsl:function name="tr:target-base-name" as="xs:string"> I get the attached paths.xml which seems ok and where my clade is resolved if in cascade/xsl/paths.xsl I use your stock $content/@base <xsl:function name="tr:target-base-name" as="xs:string"> I get Message: An empty sequence is not allowed as the result of function and indeed if I inspect $content/@name it is a '' Thanks as always, __peppo |
I’m afraid I still cannot reproduce it. Can you send me the conf file that you’re using? |
my transpect-conf.xml was attached to my previous mail. On Wed, May 25, 2016 at 1:49 PM, Gerrit Imsieke [email protected]
|
If you commented to the issue via email and attached something, maybe the attachment didn’t make it to this page, #1 |
The function tr:target-base-name in paths.xsl returns a null string, causing an error in the calling paths.xpl.
Changing the function return value from $content/@base to $content/@name apparently solves the problem, but I don't know if this has other side effects.
Cheers
__peppo
The text was updated successfully, but these errors were encountered: