cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <>
Subject Re: [RT] The environment abstraction, part II
Date Tue, 31 Jan 2006 19:48:48 GMT
Sylvain Wallez wrote:
> Sorry, but I still fail to see how this changes anything. It makes it 
> easier to develop with Cocoon as using the standard servlet API rather 
> than with a "proprietary clone" eases the learning process and 
> facilitates the integration with 3rd-party libraries. But does it change 
> something for the internal code? I fail to see how.
We get rid off the whole o.a.c.environment package - and this is the
another step to make the core cleaner. I can imagine a lot of changes
based on this one making the internal handling of requests easier to
understand and implement.

> I never said it doesn't make sense, rather the contrary. But there's a 
> difference IMO between "let's use the standard servlet API" and "let's 
> fire up a servlet engine to process a simple XML pipeline".
Sure, but see my latest response to Daniel showing some use cases where
you need the whole servlet engine. And I of course web apps have their
servlet engine running, so there is only the cli left. But starting
jetty inside is really a small thing and totally transparent from a user


Carsten Ziegeler - Open Source Group, S&N AG

View raw message