cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <giac...@apache.org>
Subject RE: Migration report from Excalibur Event to RunnableManager
Date Tue, 09 Nov 2004 18:29:14 GMT
On Tue, 9 Nov 2004, Carsten Ziegeler wrote:

> Giacomo Pati wrote:
>>
>> I know many of you don't see why this has any importance nor
>> why that should happen. Most of us run Cocoon in Jetty or
>> Tomcat. But there are also users with BWL and WAS which run
>> Cocoon there in. Recently a commercial app servers vendor has
>> begun to "sandbox" (via RACF!) the deployed servlets and has
>> inhibited thread creation (IIRC the J2EE spec says "your app
>> components may not spawn their own threads". By the
>> single-class-for thread-creation approache used by the
>> RunnableManager we can point them to where to relax the
>> sandboxing to make Cocoon run again. I have evangelized
>> people to use Cocoon as many of aou have as well. Now some of
>> them need to migrate onto the app server release mentioned
>> above out of strategic directions in their companies and of
>> course they expect some support/help/suggestions.
>>
> Hmm, not sure what's best here - but afaik doing a release of
> excalibur-store might be not possible given the current time
> frame, so why not copy the source of the class for now,
> and provide at the same time a patch to excalibur? As soon
> as they're doing a release we can remove our copy again.

That's exactly what I feard. Ok, I'll copy it over and send them a 
patch.

-- 
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com

Mime
View raw message