>> From: [EMAIL PROTECTED]
>>
>> If we remove the ComponentManagerProxy this problem is solved.
>
> I'm fine with removing the proxy, but can this problem be solved in the
> CocoonComponentManager instead? For example by making it aware of the
> proxy? Or by making it release the requestlifecycl
> [EMAIL PROTECTED] wrote:
>> The lookup/release add/remove the component to/from an ArrayList. If you
>> have a lot of Components which lookup other Components inside the
compose
>> method the List can be really big. If you have a lot of SubSitemaps
which
>> use many InputModules it grows an
Hi all,
after the Go Life of the new version of the BASF eCommerce Application,
running on top of Cocoon 2.1.2 we had a special performance effect.
After a restart of the server the startpage of the portal has a response
time of 70ms. After one day of work and a lot of page hits the response
time
Hi all,
I post this also to the Avalon list, because while tracking this
SitemapSource issue I found a Avalon Logging issue also.
Ok, what happen:
Calling a Cocoon Source "cocoon://." the Pipeline inside the Sitemap is
called twice. The reason is the following code inside the
SitemapSourceFac
you can also tryalso work with jdk1.3.
http://www.cs.berkeley.edu/~mdw/proj/java-nbio/
should also work with jdk1.3.
Volker
Hi, are there any ServerSocketFactory implementations in cornerstone that
uses the nio in jdk1.4? are there any avalon applications using it? I heard
the nio implementati
