kesh...@us.ibm.com wrote:
> Conceptually the changes would all be local to xsl:variable. But I find
> myself nervous about whether and how they would propagate through the
> rest of the system -- whether we might wind up relaxing typechecking
> elsewhere and losing some of the strength of error de
> Is it that big an ask to be able to set a variable from an extension
element?
Specifically, to set a variable to something other than XPath-compatable
data, since of course the syntax you show already works for result tree
fragments...
... I'm really not sure. Probably worth drafting a prot
verly complex or have any impact on any other
part of Xalan???
--- On Mon, 16/11/09, kesh...@us.ibm.com wrote:
> From: kesh...@us.ibm.com
> Subject: Re: Advanced Extension Element Question
> To: xalan-dev@xml.apache.org
> Received: Monday, 16 November, 2009, 3:43 PM
> I'm
>
I'm still not sure I understand why you feel you have to express this as
extension elements, when extension functions can already do what you
(appear to) need?
__
"... Three things see no end: A loop with exit code done wrong,
A semaphore untested, And the ch
Jenkins
> Subject: Re: Advanced Extension Element Question
> To: xalan-dev@xml.apache.org
> Received: Sunday, 15 November, 2009, 8:49 AM
> damn it...every single avenue I go
> down for adding a variable value from an extension element
> is a dead end (and I'm pullin' some cra
= childPopulatedXPath.execute(xctxt, sourceNode, this);
Thoughts/Comments?
Doing this allows for some pretty cool extension elements to be built which
would really take Xalan to another level.
Cheers
Adam
--- On Sat, 14/11/09, kesh...@us.ibm.com wrote:
> From: kesh...@us.ibm.com
> Sub
> Can anyone tell me if there's any way to add an object (not node or
> tree fragment) variable to the variable stack from an extension element?
>From an extension _element_... I don't think so.
>From an extension _function_, yes. If the returned value is not an
instanceof one of the types cal
bject into the local variable stack under a given name
so that I can reference it, for example in an
--- On Fri, 13/11/09, Adam Jenkins wrote:
> From: Adam Jenkins
> Subject: Advanced Extension Element Question
> To: xalan-j-us...@xml.apache.org, xalan-dev@xml.apache.org
> Receiv
Hi All,
I'm just wondering if there is a way to place a java object (not a tree
fragment) into the context output results from an extension element, and have
it stay as an object (and not have it turned into a Document node).
Here is the exact use case. I have a custom extension that creates a
