cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grzegorz Kossakowski <>
Subject Re: Unified expression handling and unified object model
Date Thu, 22 Mar 2007 13:08:44 GMT
Peter Hunsberger napisaƂ(a):
> On 3/21/07, Grzegorz Kossakowski <> wrote:
> That is essentially what we are already doing.  The issue isn't how to
> deal with the results (true or false) of the validation pipeline.  The
> issue is how to run the validation pipeline and get the results in the
> first place.  The difference of whether you can get at the status code
> or whether you get an attribute is more-or-less orthogonal to the real
> problem (though it helps clean things up a little). What you need to
> focus on is how do your fork a process in the middle of an action and
> run a pipeline and then reuse the results of that pipeline in the
> generation process that follows the action.
> Currently you can't capture directly into a SaxBuffer (more on that
> below), so that would be a good way to clean up a bit of the code bse.
> However, I think you'd have to create a new function and deprecate
> the current processPipelineTo for backwards compatibility?

I don't think that any incompatibility would be introduced. The only
change that is needed is to return status code as result of
processPipelineTo. Now, AFAIK this result value is just undefined so
nobody relays on it. Nothing else would be changed.

> Currently, with a positive validation (true) you can just trash the
> results of the validation.  If you have errors we capture them in an
> object that latter essentially replays them as SAX events. (We don't
> directly capture the Sax events, rather we capture the error text in
> an object, but it's more or less the same thing). At no point do we
> ever serialize the results of the side pipeline and then deserialize
> them to aggregate them back into another pipeline.  As a result the
> side pipeline doesn't have a normal Cocoon life cycle, the serializer
> does nothing, no headers are built, no output is generated, the side
> pipeline was run and SAX events were examined but that's the end of
> it. I think this is what you're more-or-less proposing but in a little
> cleaner way (and the code comes with the Cocoon base).

I'm lost here now.
I propose to use _valid_ Cocoon's pipeline for validation but internal
one, invoked from flowscript. Validation report would be included in XML
returned by this pipeline. So you have to have normal serializer at the
end of your validating pipeline to serialize report. Also status code is
set according the result of validation (failed/succeed) so the caller
could easily decide what to do next without investigating into details
of actual report.
If validation succeed it's usually no report to return so validation
pipeline would just return dummy:
<validationSucceed/> XML fragment.

My main point was, that you can achieve exactly the same effect without
the use of output modules and correct pipeline (not missing e.g.
serializer). Don't you?

Grzegorz Kossakowski

View raw message