Hi mate, IIRC, but I could be wrong, the reason is more historical than real need, to make APIs elastic enough for both Sitemap/programmatic executions.
Anyway, there are still some things I contine getting confused about the APIs, but I'll discuss them in a separated thread. Thanks a lot for the feedbacks, all the best! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Fri, Mar 30, 2012 at 12:57 AM, Christian Grobmeier <grobme...@gmail.com> wrote: > Hello folks, > > I was looking at cocoon3 Pipeline interface. I saw: > > setup(OutputStream outputStream) > setup(OutputStream outputStream, Map<String,Object> parameters) > > It seem one always needs to call setup() (which makes sense). But why > is there a method like this? Couldn't it be the execute method which > takes the OutputStream? > > execute(OutputStream outputStream) > execute(OutputStream outputStream, Map<String,Object> parameters) > > One would get rid of setup - this feels more natural to me at first glance. > > Cheers > Christian > > > > -- > http://www.grobmeier.de > https://www.timeandbill.de
