You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The rendering XSLT for printedVariable is currently expecting @index to be an integer, rather than integerOrVariableRef, and is consequently blowing up if the attribute is a variable reference.
The text was updated successfully, but these errors were encountered:
This one is going to require some effort to fix. The current rendering of printedVariable does all of the variable de-referencing within the XSLT. Handling integerOrVariableRef is non-trivial (as one can see from the corresponding implementation of this within the Java classes). I think it might be better to add an XML filter to the rendering pipeline the computes the final value for each printedVariable (using the existing Java logic) and substitutes the result into the XML before it gets passed to the rendering XSLT. That would simplify the amount of work the XSLT has to do here.
I have added a guard condition to prevent rendering from blowing up if
@index is a variable reference. Rendering will now continue, but a
message will be shown instead of the de-referenced value.
The rendering XSLT for
printedVariable
is currently expecting@index
to be an integer, rather thanintegerOrVariableRef
, and is consequently blowing up if the attribute is a variable reference.The text was updated successfully, but these errors were encountered: