On Mon, 2003-08-25 at 14:24, Michael Melhem wrote: > On Sun, Aug 24, 2003 at 07:39:58PM +0200, Carsten Ziegeler wrote: > > Hi, > > > > it seems that the CommandManager of the Excalibur Event package > > is not working as expected. If you add a command to the sink > > of the CommandManager it's never executed. > > Unfortunately, this code is used in the ContinuationsManager > > for testing against expired continuations. But the > > execute() method of ContinuationInterrupt is never invoked! > > > > So, it seems that there is a bug somewhere in the event package > > and our manager is not working properly. > > > > Why is the CommandManager instantiated in Cocoon.java, put > > into the Context and get out of it in contextualize in the > > ContinuationManagerImpl? The CommandManager is only used > > there. IMHO it would be much cleaner to either move the > > initialization to the ContinuationManagerImpl or to make > > a real component out of it. Passing components in the context > > seems to be a hack, no? > > > > I think, a simple solution would be to switch to the cornerstone > > scheduler component. This component works (see the scheduler sample > > in the scratchpad) and removing the CommandManager usage should also > > fix the shut-down problems with Tomcat entered as a bug that annoyes > > many users. > > But if someone is able to fix both problems in the event > > package I'm fine with that as well of course. > > IIRC, the cornerstone scheduler was the orginal scheduler > used to expire continuations. I would need to delve into > the mail archives to retreive the reason that it was changed.
I just did, see here: http://marc.theaimsgroup.com/?l=xml-cocoon-dev&w=2&r=1&s=remove+need+for+cornerstone+jars&q=b more specifically: http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104628525923843&w=2 -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED]
