But if it does not implement Poolable - what does it mean then ?
Nothing bad :)
It just means that everytime your action is used a new instance of your
action class is created.
Now if you make your action implement Poolable (which is just a marker
interface) then cocoon will manage a pool
DEBUG (2004-02-02) 15:55.06:770 [sitemap] (/test/report-save)
PoolThread-9/DefaultComponentFactory: ComponentFactory decommissioning
instance of com.***.ReportAcceptor.
I keep getting those messages in my sitemap.xmap. What does it really mean and
how can I get rid of it. The action is quite
Leszek Gawron wrote:
DEBUG (2004-02-02) 15:55.06:770 [sitemap] (/test/report-save)
PoolThread-9/DefaultComponentFactory: ComponentFactory decommissioning
instance of com.***.ReportAcceptor.
Does your action implement the Poolable interface? If it doesn't then
there is no point setting
Does your action implement the Poolable interface? If it doesn't then
there is no point setting the pool parameters (at least in 2.0.4 it
doesn't) because Action inherits straight from Component.
It does not implement Poolable interface. Searching for the solution I just
copied the declaration
Leszek Gawron wrote:
Does your action implement the Poolable interface? If it doesn't then
there is no point setting the pool parameters (at least in 2.0.4 it
doesn't) because Action inherits straight from Component.
It does not implement Poolable interface. Searching for the solution I just
