<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Balz<br>
<br>
Please see my comments inline below<br>
<br>
Am 28.02.14 10:08, schrieb basZero:<br>
</div>
<blockquote
cite="mid:CAOXzDSEyefuuPHpjNTxsn3uoLPKsux8kOORNpRRui_QNE8jF5A@mail.gmail.com"
type="cite">
<pre wrap="">Hi,
as you know, Yanel performs the XSLT (Transformation of XSL to temporary
Java Class) for EACH request.
I would like to ask, whether there is anybody out there who has played with
these two alternative approaches:
1) extend XSLT Processor in a way, that it keeps a list of XSLs including
timestamps and only does the transformation, if the XSL has changed. Hence:
reuse the java classes from earlier if nothing changed.</pre>
</blockquote>
<br>
At the moment we use<br>
<br>
<dependency groupId="xalan" artifactId="xalan"
version="2.7.0"/><br>
<br>
but I am not sure whether what you are asking has actually anything
to do with Xalan itself, but<br>
rather how we instantiate the XSLTs inside<br>
<br>
<br>
src/impl/java/org/wyona/yanel/impl/resources/BasicXMLResource.java<br>
<br>
It seems to me that we would have to introduce so called Templates
as described in<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.javaworld.com/article/2073394/java-xml/transparently-cache-xsl-transformations-with-jaxp.html">http://www.javaworld.com/article/2073394/java-xml/transparently-cache-xsl-transformations-with-jaxp.html</a><br>
<br>
Maybe you can give it a try.<br>
<br>
Independent of the caching the following performance hints might
also improve your situation<br>
<br>
<a class="moz-txt-link-freetext" href="https://xalan.apache.org/old/xalan-j/faq.html#faq-N10175">https://xalan.apache.org/old/xalan-j/faq.html#faq-N10175</a><br>
<br>
HTH<br>
<br>
Michael<br>
<blockquote
cite="mid:CAOXzDSEyefuuPHpjNTxsn3uoLPKsux8kOORNpRRui_QNE8jF5A@mail.gmail.com"
type="cite">
<pre wrap="">
This option would still have the advantage that you can change/patch XSL
files in the running system and see the changes immediately.
2) There is an official XSLT processor mode called "cached". In this mode,
the XSLT processor only performs the XSLT once and keeps the generated java
classes for the lifetime of the JVM. This is certainly the fastest way of
having XSLT in a system, but any changes to XSLs are of course ignored once
the XSLT has happened. So this is a disadvantage.
I would be interested in some hands-on experience for option 1).
Cheers, Bas
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>