Re: Upgrading Cocoon from 2.1.7 to 2.1.9

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

Re: auth-protect not defined for act

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

Re: auth-protect not defined for act

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.jar

Return Error Code Based on Pipeline Content

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 - map:match=put-request map:generate type=request/ map:transform src=setupSqlQuery.xsl/ map:transform type=sql/ map:transform src=transformSqlResults.xsl/

Re: Upgrading Cocoon from 2.1.7 to 2.1.9

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