Issue with recognizing preview or generate mode in XSL

Our requirement was to recognize the preview or generate mode in XSL.
Hence we stored the value of '$CONTEXT{preview}' in a variable and tried to access its value
When we printed the value of the "isPreview" variable , it gave an output of true or false depending on the mode(preview or generate).
However when we tried to access the same using a conditional statement (,,) , it would not execute.We tried to analyze this and we strangely found that the length of the variable was 17. We tried to get the contents of the variable and stangely "$CONTEXT{preview]" was part of it. However on printing the variable , it gave us only true or false.
If anyone has faced this issue before or has any insights on the same , Kindly let us know.

Find more posts tagged with

Comments

Adam Stoller

Our requirement was to recognize the preview or generate mode in XSL.
Hence we stored the value of '$CONTEXT{preview}' in a variable and tried to access its value
When we printed the value of the "isPreview" variable , it gave an output of true or false depending on the mode(preview or generate).
However when we tried to access the same using a conditional statement (<xsl:if>,<xsl:when>,) , it would not execute.We tried to analyze this and we strangely found that the length of the variable was 17. We tried to get the contents of the variable and stangely "$CONTEXT{preview]" was part of it. However on printing the variable , it gave us only true or false.
If anyone has faced this issue before or has any insights on the same , Kindly let us know.

You say 'strangely[sic] "$CONTEXT{preview]" was part of it' - however a more accurate statement would be that it was "all" of it - hence the 17 character length. Should we assume that the open-curly-branch with closing-square-bracket is just a typo in the forum - or is that literally how it looks in your code (that would explain why it comes out that way, but somehow I doubt you missed such an obvious typo in the actual code - right?

Perhaps if you showed the complete XSL code that you were using to reference this variable - exactly as it appears in your code - someone might be able to determine why the variable isn't getting evaluated.

Rick Poulin

Context and page scope variables are only expanded *after* the XSL rendering occurs. Thus, if you want the value to be available for conditional statements in XSL, you'll have to use a Java External to read context.isPreview() and pass that value back in the response Document.