[ https://issues.apache.org/jira/browse/XALANJ-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788785#action_12788785 ]
Michael Glavassevich commented on XALANJ-2510: ---------------------------------------------- Henry politely offered you constructive critcism for your patch. If you're not interested in continuing that is certainly your choice, but the tone of your responses isn't helping your case. Whatever your disagreements keep it to a technical discussion. Lets be civil. > Ability to set non tree fragment variable using an extension element (PATCH > SUPPLIED) > ------------------------------------------------------------------------------------- > > Key: XALANJ-2510 > URL: https://issues.apache.org/jira/browse/XALANJ-2510 > Project: XalanJ2 > Issue Type: Improvement > Security Level: No security risk; visible to anyone(Ordinary problems in > Xalan projects. Anybody can view the issue.) > Components: Xalan-extensions > Affects Versions: The Latest Development Code > Reporter: Adam Jenkins > Fix For: The Latest Development Code > > Attachments: XALANJ-2510.patch > > > When using extension elements, there is no way to set a non XRTreeFrag > related variable. > For example, say you have: > <xsl:variable name="myvar"> > <my:extension someAttribute="somevalue"/> > </xsl:variable> > If my:extension wants to set a tree fragment, string or nodeset into myvar, > that's not a problem, however if it wants to set a java object, currently > there is no mechanism for that (any java object passed either returned from > the method or passed to XSLProcessorContext.outputToResultTree is > toString()'ed before being passed back to the ElemVariable.getValue() method). > The proposed change (patch supplied) is to supply an optional variable on > ElemVariable.java whereby child extension elements can call up to their > parent and set an XPath to be evaluated after the extension element has > finished processing. > This requires only very minor modification to the ElemVariable.getValue > method to check this variable. > This also ensures that this is optional functionality and will not affect > that basic Xalan processing. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org For additional commands, e-mail: xalan-dev-h...@xml.apache.org