pipelineComponent scope troubles (was: Re: Refactoring cocoon-thread)

2007-09-10 Thread Grzegorz Kossakowski
Giacomo Pati pisze: > > > Grzegorz Kossakowski wrote: >> Giacomo Pati pisze: > >> Are you sure you are running latest trunk? > > Hmm.. if a 'svn up' isn't enough to get there, tell me how else. It's enough, sorry for asking dumb questions. >> You are having a trouble with the code handling >

Re: Refactoring cocoon-thread

2007-09-10 Thread Giacomo Pati
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Grzegorz Kossakowski wrote: > Giacomo Pati pisze: >> >> 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. >> I was trying to find the other "

Re: Refactoring cocoon-thread

2007-09-10 Thread Grzegorz Kossakowski
Giacomo Pati pisze: > > > 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. > > I was trying to find the other "incompatible changes in trunk" as since I've > updated my repo my app > isn'

Re: Refactoring cocoon-thread

2007-09-09 Thread Giacomo Pati
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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. I was trying to find the other "incompatible changes in trunk" as since I've updated my repo

Re: Refactoring cocoon-thread

2007-08-20 Thread Carsten Ziegeler
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. I

Re: Refactoring cocoon-thread

2007-08-20 Thread Grzegorz Kossakowski
Carsten Ziegeler pisze: 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

Refactoring cocoon-thread

2007-08-20 Thread Carsten Ziegeler
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.thr