Andreas Hochsteger wrote:
> Hi,
>
> is there something we need to take care of, when upgrading Cocoon from
> 2.1.7 to 2.1.9?
>
> These are the most important things we are currently using:
> * FlowScript
> * JXTemplates
> * Cocoon Forms
> * Portal Engine
> * WebDAV Access (TraversableSourceDescri
Andrew Stevens wrote:
[me]
I did the default build, so I had assumed Yes. How would I recognise it?
Well, for starters, there'll be a cocoon-authentication-fw-block.jar in
build/webapp/WEB-INF/lib...
That's there:
$ locate cocoon-authentication-fw-block.jar
/usr/src/cocoon-2.1.8/build/webap
Peter Flynn wrote:
> Andrew Stevens wrote:
> [me]
>>> I did the default build, so I had assumed Yes. How would I recognise it?
>>
>> Well, for starters, there'll be a cocoon-authentication-fw-block.jar
>> in build/webapp/WEB-INF/lib...
>
> That's there:
>
> $ locate cocoon-authentication-fw-block
Is it possible to return an error code based on the content in the pipeline?
What I have currently is something similar to the following -
What I would like to be able to do is examine the content of the sql
transform and determine a success or failure of the operation. Based on
this r
Jason Johnston schrieb:
Andreas Hochsteger wrote:
Hi,
is there something we need to take care of, when upgrading Cocoon from
2.1.7 to 2.1.9?
These are the most important things we are currently using:
* FlowScript
* JXTemplates
* Cocoon Forms
* Portal Engine
* WebDAV Access (TraversableSource
Le 10 avr. 06 à 04:51, Daniel Curran a écrit :
...What I would like to be able to do is examine the content of the
sql transform and determine a success or failure of the operation.
Based on this result I would like to be able to send an error.
If the operation was completed successfully I
