The first line and the third seem to differ in resource:// and
logicsheet:resource://. I do not know anything about xsp, but seems to me that
it is caching to different things for the xsl (also it is cached as a different
class both times, so I would not bother if I were you).
About the second line, it is the compiled Java XSLT that is cached.
Regards Ard
When I ask for some pages with my Cocoon webapp, and I ask for current status
after that, here is what I got :
<group name="org.apache.cocoon.components.store.impl.DefaultTransientStore
(hash = 0x39474b)">
<value name="cached">
<line>resource://org/apache/cocoon/components/language/markup/xsp/java/xsp.xslorg.apache.xalan.processor.TransformerFactoryImpl
(class: [ Ljava.lang.Object;)</line>
<line>file:/usr/local/jakarta-tomcat-5.5.12/webapps/toto/baby/xsl/myml2html.xslorg.apache.xalan.xsltc.trax.TransformerFactoryImpl
(class: [Ljava.lang.Object;)</line>
<line>logicsheet:resource://org/apache/cocoon/components/language/markup/xsp/java/xsp.xsl
(class: org.apache.cocoon.components.language.markup.Logicsheet)</line>
</value>
The second <line> is the cache of my own XSLT. Is this the cache of the .xsl
file itself or is it the cache of the compiled Java XSLTC ?
Beyond that, I don't see the difference between the first <line> and the third
one.
I guess it is related to the cache of the XSLT file which was used to transcode
my XSPs into some Java class but it's not clear the role of each.
Regards,
2006/7/3, Ralph Goers <[EMAIL PROTECTED]>:
Cocoon Man wrote:
> Actually, what is not clear for me is the relation there is between
> the fact that an XSP is a Poolable component (which means there is a
> pool of XSPs stored somewhere by Cocoon) and the fact that XSP are
> stored by Transient-store.
> I don't understand why I have to set some *pool-max* parameter for the
> <map:generator name="serverpages"> component and some *maxobjects* for
> the transient-store which handles previously loaded generators.
The ServerPagesGenerator needs to be pooled so that multiple requests
can simultaneously use it to generate XSPs (or to even locate them in
the store). If your system allows 10 concurrent users running the same
request then you would want 10 ServerPagesGenerators in the pool. This
keeps you from creating and destroying them on every request, which is
fairly expensive because each one has to be configured from the XML and
then setup various companion components.
The store is used the cache the output of the generator, so subsequent
requests with the same input, and which would get the same output, can
simply be served by returning the cached result.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
