You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Olivier Richaud <ri...@cstb.fr> on 2000/09/28 14:10:24 UTC

Turbine Pool and xsp

I've been using XSP for a while now, and since version 1.8 I've noticed that
turbine has been
incorporated to Cocoon. Well, but I don't use any connection pool at this
level and I don't want
to load turbine. I decided to omit turbine-pool.jar in my classpath  and
commented out
portions of cocoon.properties (those relevant to turbine). But at runtime,
Cocoon complains and outputs this message (for short :but where's turbine):

java.lang.RuntimeException: Error creating
org.apache.cocoon.processor.xsp.XSPProcessor: make sure the needed classes
can be found in the classpath
(org/apache/turbine/services/resources/TurbineResourceService)
 at org.apache.cocoon.framework.Manager.create(Manager.java:114)
 at org.apache.cocoon.framework.Router.init(Router.java:80)
 at org.apache.cocoon.framework.Manager.create(Manager.java:101)
 at org.apache.cocoon.Engine.(Engine.java:171)
 at org.apache.cocoon.Engine.getInstance(Engine.java:218)
 at org.apache.cocoon.Cocoon.init(Cocoon.java:141)
 at com.caucho.server.http.Application.loadServlet(Application.java:1274)
 at com.caucho.server.http.Invocation.getServlet(Invocation.java:302)
 at com.caucho.server.http.AbstractRequest.service(AbstractRequest.java:411)
 at com.caucho.server.http.VirtualHost.service(VirtualHost.java:422)
 at com.caucho.server.http.Request.dispatch(Request.java:212)
 at
com.caucho.server.http.RunnerRequest.handleRequest(RunnerRequest.java:313)
 at
com.caucho.server.http.RunnerRequest.handleConnection(RunnerRequest.java:260
)
 at com.caucho.server.TcpConnection.run(TcpConnection.java:142)
 at java.lang.Thread.run(Thread.java:484)



Olivier Richaud
CSTB
office: +33 4 93 95 67 24
mobile: +33 6 87 52 53 17
www: http://cic.cstb.fr


Cache / Store madness

Posted by Olivier Richaud <ri...@cstb.fr>.
I know this question has been raised many times (too many), so I first
apologize for raising
the question.

OK, let's start : My problem is that most of my pages are heavily using EJB
to get generate
dynamic content. In that case, I first make a transformation that inserts
XSP code and then I
transform this new XML to HTMl with a second transformation.

The fact is when I use CocoonCache instead of NoCache, my pages are not
refreshed ! Which is, you must admit, obviously irrelevant for dynamic
pages. On the other hand, I have obtained good performances with CocoonCache
and poor performances with NoCache.

I wanted to make my own opinion, and I decided to make my mind and used the
profiler. I admit that the XSP processor has a lot of work, but the
XSLTProcessor (I use Xalan, what about XT) is even slower.

I'm also wondering what is the role played by the MemoryStore. I took a look
at Cocoon.xml and i noticed my pages are cached by the store. Could anybody
tell what is the difference between the store and the cache.

Well, all in all, a good advice on how to tune correctly Cocoon would be
very appreciated.

Thanks in advance.

Olivier Richaud
CSTB
office: +33 4 93 95 67 24
mobile: +33 6 87 52 53 17
www: http://cic.cstb.fr