Vadim Gritsenko pisze:
> Carsten Ziegeler wrote:
>> Grzegorz Kossakowski wrote:
>> Yepp, but unfortunately too many people rely on these side-effects :(
>
> Is there place where differences between servlet: and cocoon: sources
> are described? Or, at least, where servlet: source is described?
For
Joerg Heinicke pisze:
> It seems we do not even know the requirements. How do you want to decide
> about architecture without them? My guess - since Cocoon is just a
> framework - you merely get the requirements from real applications built
> on it. Why can't we wait until the people get used to th
Carsten Ziegeler wrote:
Grzegorz Kossakowski wrote:
Thinking more about incompatibilities between cocoon: and servlet: protocols
I'm getting an
impressions that they are not such fundamentally different when it comes to
their usage schemes. Of
course they differ in many details but as Reinhard
On 07.11.2007 15:52 Uhr, Grzegorz Kossakowski wrote:
Now, at some point we have to break compatibility to get a cleaner
architecture and an even better way of doing things. Perhaps removing
sub sitemaps is one of these things, perhaps not.
Before we start to think about migration path and embe
Grzegorz Kossakowski wrote:
> Carsten Ziegeler pisze:
>> Yes, that's true. Now, at some point we have to break compatibility to
>> get a cleaner architecture and
>> an even better way of doing things. Perhaps removing sub sitemaps is one
>> of these things, perhaps not.
>
> Before we start to thi
