cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <>
Subject Re: Refactoring cocoon-thread
Date Mon, 20 Aug 2007 09:44:18 GMT
Looking at the code I think we should fix some more issues with the
thread module:

Some setter methods have been added to the ThreadPool interface. I think
this is an immutable service, therefore I would like to remove the
setter methods again.

The Queue interface should not be part of the api. It's just used

The RunnableManager#createPool(String name,...) should return the
created pool and we should add a getPool(String name) to the
RunnableManager interface as well.

The shutdown method should be removed from the ThreadPool interface as
all pools are managed (and therefore shutdown) by the runnable manager


Carsten Ziegeler wrote:
> We've already done some incompatible changes in trunk, I would like to
> add one more which should not effect most of our users.
> The current cocoon-thread-api and -impl core modules use the same
> package name: o.a.c.components.thread. I propose to change this to
> o.a.c.thread for the api and o.a.c.thread.impl for the the
> implementation. The whole thread stuff is independent from Cocoon (and
> also Spring) and therefore I think it makes sense to have clean package
> names.
> If noone objects I'll do the changes in the next days.
> Carsten

Carsten Ziegeler

View raw message