Simone Tripodi wrote:
Hi Reinhard,
I'm sorry I was not very clear, as reloader I mean a sort of XSLT
watchdog that reload it when it's changed - it's a feature already
present in oldest Cocoon's version, Sylvain spoke about it in the Jira
issue
There are two ways you can consider to reload
Hi Reinhard,
In my mind makes more sense reading the XSLT once, an
org.apache.cocoon.pipeline.component.sax.XSLTTransformer instance
should be reusable and it shouldn't read the same XSLT each time it
has to perform a transformation. Please correct me if I'm wrong!
no makes sense! See
Simone Tripodi wrote:
Hi Reinhard,
In my mind makes more sense reading the XSLT once, an
org.apache.cocoon.pipeline.component.sax.XSLTTransformer instance
should be reusable and it shouldn't read the same XSLT each time it
has to perform a transformation. Please correct me if I'm wrong!
no
Hi Reinhard,
I'm sorry I was not very clear, as reloader I mean a sort of XSLT
watchdog that reload it when it's changed - it's a feature already
present in oldest Cocoon's version, Sylvain spoke about it in the Jira
issue
Hi Reinhard!!!
thank you for your reply!!!
I'll proceed working on all these small issues - and I'll provide the
patches ASAP :)
I'm sorry for my rather long response times (e.g. your
XIncludeTransformer stuff) but I'm very busy ATM. The
XIncludeTransformer will take me some time to review
Hi Reinhard/everybody,
I would like to argue with you some simple point about the
org.apache.cocoon.pipeline.component.sax.XSLTTransformer, sharing
ideas and collecting feedbacks.
Note: my attention is focused more just on the basic pipeline API use,
the test case (mine!!!) is the case where a
Simone Tripodi wrote:
Hi Reinhard/everybody,
I would like to argue with you some simple point about the
org.apache.cocoon.pipeline.component.sax.XSLTTransformer, sharing
ideas and collecting feedbacks.
Note: my attention is focused more just on the basic pipeline API use,
the test case
