You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-users@xalan.apache.org by Tomas Studva <ts...@gmail.com> on 2007/10/12 17:57:53 UTC
Can someone explain Xalan XSLT execution
Can someone explain Xalan XSLT execution in details, please. Or give link to
some good docs.
Tomas
--
View this message in context: http://www.nabble.com/Can-someone-explain-Xalan-XSLT-execution-tf4614181.html#a13177022
Sent from the Xalan - J - Users mailing list archive at Nabble.com.
Re: Can someone explain Xalan XSLT execution
Posted by Tomas Studva <ts...@gmail.com>.
I know that document. I've read that before.
Mukul Gandhi wrote:
>
> You might find this information useful:
> http://xml.apache.org/xalan-j/design/design2_0_0.html
>
> On 10/12/07, Tomas Studva <ts...@gmail.com> wrote:
>>
>> Can someone explain Xalan XSLT execution in details, please. Or give link
>> to
>> some good docs.
>>
>> Tomas
>
>
> --
> Regards,
> Mukul Gandhi
>
>
--
View this message in context: http://www.nabble.com/Can-someone-explain-Xalan-XSLT-execution-tf4614181.html#a13187960
Sent from the Xalan - J - Users mailing list archive at Nabble.com.
Re: Can someone explain Xalan XSLT execution
Posted by Mukul Gandhi <ga...@gmail.com>.
You might find this information useful:
http://xml.apache.org/xalan-j/design/design2_0_0.html
On 10/12/07, Tomas Studva <ts...@gmail.com> wrote:
>
> Can someone explain Xalan XSLT execution in details, please. Or give link to
> some good docs.
>
> Tomas
--
Regards,
Mukul Gandhi
Re: Can someone explain Xalan XSLT execution
Posted by ke...@us.ibm.com.
>> - why there is code to execute stylesheet in ElemTemplateElem.execute
method
>> and also in TransformerImpl, which and when is used
>That's a good question, but I don't know the answer. It looks like the
code in >TransformerImpl is used to match the initial template for
stylesheet processing and >also for template matching for
xsl:apply-imports, but I have no idea why the code is >organized that way.
I suspect that's mostly a historical artifact -- how the code evolved over
time -- more than a principled design decision. There are a number of
places where we had the choice of building additional layers of
interpretation/compilation or of inlining some of that code, and decisions
were driven by a mixture of what else had been written at that point (which
may have changed later), whether we thought we might need/want to make
localized tweaks for performance reasons, and so on.
Re: Can someone explain Xalan XSLT execution
Posted by Henry Zongaro <zo...@ca.ibm.com>.
Hi, Tomas.
Tomas Studva <ts...@gmail.com> wrote on 2007-10-13 05:40:48 AM:
> I cannot provide any donations to Xalan, I'm doing on my own. I'm
interested
> about interpretive execution. For me, it would be useful if you can
review
> Xalan part of this document:
> http://www.javaforge.com/proj/doc/details.do;
> jsessionid=190DC631414DA527977AF6C19BE6F42F?doc_id=36525
>
> - which branch should I look on, I am interested in XSLT 1.0 (I've been
> looking on trunk)
Yes, the main trunk is the appropriate place to look for the most
up-to-date code.
> - is execution iterative - by self managed stacks
I'm not sure I understand that question. I think you're asking whether an
instruction like xsl:apply-templates or xsl:apply-imports results in a
recursive Java method invocation of other instructions execute methods.
The answer to that question is yes, but as I said, perhaps I've
misunderstood your question. If so, can you please elaborate?
> - why there is code to execute stylesheet in ElemTemplateElem.execute
method
> and also in TransformerImpl, which and when is used
That's a good question, but I don't know the answer. It looks like the
code in TransformerImpl is used to match the initial template for
stylesheet processing and also for template matching for
xsl:apply-imports, but I have no idea why the code is organized that way.
Is it critically important to understand why the code is organized that
way? If so, it would take a bit of research into the history in the
source repository.
> - can you look and answer
> http://www.nabble.com/ElemApplyTemplates-implementation-tf4603600.html
I'll respond to your original note separately on the list.
> - I am interested only in DOM2DOM tranformation
> - I will get a better view, I am going to profile/monitor Xalan on some
xslt
> by eclipse TPTP, it will give some sequence diagram
Thanks,
Henry
------------------------------------------------------------------
Henry Zongaro XSLT Processors Development
IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
mailto:zongaro@ca.ibm.com
Re: Can someone explain Xalan XSLT execution
Posted by Tomas Studva <ts...@gmail.com>.
I cannot provide any donations to Xalan, I'm doing on my own. I'm interested
about interpretive execution. For me, it would be useful if you can review
Xalan part of this document:
http://www.javaforge.com/proj/doc/details.do;jsessionid=190DC631414DA527977AF6C19BE6F42F?doc_id=36525
- which branch should I look on, I am interested in XSLT 1.0 (I've been
looking on trunk)
- is execution iterative - by self managed stacks
- why there is code to execute stylesheet in ElemTemplateElem.execute method
and also in TransformerImpl, which and when is used
- can you look and answer
http://www.nabble.com/ElemApplyTemplates-implementation-tf4603600.html
- I am interested only in DOM2DOM tranformation
- I will get a better view, I am going to profile/monitor Xalan on some xslt
by eclipse TPTP, it will give some sequence diagram
keshlam wrote:
>
>
> "Explaining Xalan execution", in full detail, would be a small book. Even
> a
> "principles of operations" document would be nontrivial... though perhaps
> worth having, if someone had the time to work on it. At that level, the
> answer is "Yes, someone can and should, but someone has to come up with
> the
> funding so they can afford to take the time to do it -- or has to find a
> really dedicated volunteer."
>
> Right now, what we've got is the javadocs, the code, the archives of this
> mailing list, and I would guess some papers that have been published in
> the
> past that may not reflect the current implementation.
>
> Do you have specific questions? Do you have a specific level of detail
> you're looking for? Are you asking about interpretive operation, compiled,
> or both?
>
>
>
> ______________________________________
> "... Three things see no end: A loop with exit code done wrong,
> A semaphore untested, And the change that comes along. ..."
> -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish
> (http://www.ovff.org/pegasus/songs/threes-rev-11.html)
>
--
View this message in context: http://www.nabble.com/Can-someone-explain-Xalan-XSLT-execution-tf4614181.html#a13188073
Sent from the Xalan - J - Users mailing list archive at Nabble.com.
Re: Can someone explain Xalan XSLT execution
Posted by ke...@us.ibm.com.
"Explaining Xalan execution", in full detail, would be a small book. Even a
"principles of operations" document would be nontrivial... though perhaps
worth having, if someone had the time to work on it. At that level, the
answer is "Yes, someone can and should, but someone has to come up with the
funding so they can afford to take the time to do it -- or has to find a
really dedicated volunteer."
Right now, what we've got is the javadocs, the code, the archives of this
mailing list, and I would guess some papers that have been published in the
past that may not reflect the current implementation.
Do you have specific questions? Do you have a specific level of detail
you're looking for? Are you asking about interpretive operation, compiled,
or both?
______________________________________
"... Three things see no end: A loop with exit code done wrong,
A semaphore untested, And the change that comes along. ..."
-- "Threes" Rev 1.1 - Duane Elms / Leslie Fish
(http://www.ovff.org/pegasus/songs/threes-rev-11.html)