cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexandre Victoor <>
Subject RE: Cocoon1 -> Cocoon2
Date Wed, 13 Feb 2002 14:10:49 GMT
You are welcome :)
But you have to look at the memory aspect too...
A new instance of the generator is created at each request and so the 
amount of memory allocated keeps increasing.
With cocoon2 you can also use a servlet as a generator. It's certainly not 
the best solution neither but since you have already a servlet...
Good luck


At 14:56 13/02/2002 +0100, you wrote:
>Thanx Alex. I guess this was exactly what I needed.
>I assume that from the performace point of view this
>is not the best solution, but I right now I already have a huge
>amount of code in a servlet. In order to make the pages
>configurable, I ported the whole thing pretty easily
>to Cocoon1. I converted my servlet into a Producer.
>Now I'm trying to do the same thing for
>Cocoon2. If I could, I would start the whole thing all
>over again, but I don't have the time. :(
>I'm also concerned about speed, so I'm doing some
>speed comparison: old servlet/C1/C2.
>Thanks again, Geza
> > -----Original Message-----
> > Here is a dummy generator that parses a string and gives the
> > sax events to  cocoon. Hope that is what you need.

Please check that your question has not already been answered in the
FAQ before posting. <>

To unsubscribe, e-mail: <>
For additional commands, e-mail: <>

View raw message