Grzegorz Kossakowski wrote:
Leszek Gawron pisze:
Caused by: org.apache.cocoon.CascadingIOException: If you see this
exception you probably called
Source.getInputStream even though the source reported proper validity.
The only way to solve this
is to implement a resource heavy version of postable source.:
javax.servlet.ServletException: If
you see this exception you probably called Source.getInputStream even
though the source reported
proper validity. The only way to solve this is to implement a resource
heavy version of postable
source.
this probably means we will not be able to implement fully pipelined
servlet services.. I have reverted the change we did at GT.
Very unfortunate news but I don't think situation is hopeless.
Anyway, my opinion is that we should just start with buffer and after
servlet-service stabilizes. We
could continue improving servlet protocol performance. Otherwise, if we are
going to complicate it
now it's going to be hard to figure out what's the possible problem with
servlet protocol.
Giacomo, does everything work for you after Leszek reverted his changes?
Grek, in the case that Giacomo's answer is yes, could you please branch the
affacted modules from /tags/cocoon-2.2/???/[version] to
/branches/cocoon-2.2/???/[version] and apply your patch(es) their too? Then I
could recreate the release artifacts and we can start to test them.
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair [EMAIL PROTECTED]
_________________________________________________________________________
