That doesn't work. I suspect the problem is the "different" way this
pipeline gets invoked. It is called from authenticate() in
PipelineAuthenticator with the following code:
// invoke the source
try {
Source source = null;
try {
source =
org.apache.cocoon.components.source.SourceUtil.getSource(authenticationResou
rceName,
null,
parameters,
this.resolver);
doc =
org.apache.cocoon.components.source.SourceUtil.toDOM(source);
} catch (SAXException se) {
throw new ProcessingException(se);
} catch (SourceException se) {
throw
org.apache.cocoon.components.source.SourceUtil.handle(se);
} catch (IOException e) {
throw new ProcessingException(e);
} finally {
this.resolver.release(source);
}
} catch (ProcessingException local) {
this.getLogger().error("authenticator: " + local.getMessage(),
local);
exceptionMsg = local.getMessage();
}
I always see the logger message from this which obviously means this code is
handling the exception. So I'm pretty sure handle-errors is just not going
to work here.
Ralph
> -----Original Message-----
> From: Frank Taffelt [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 12, 2003 8:01 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Authentication Framework] handle-errors
>
>
> try to place your error handler outside your pipeline section:
>
> <map:sitemap>
>
> <map:pipelines>
>
> <map:pipeline>
> ...
> </map:pipeline>
>
> <map:handle-errors>
> <map:select type="exception">
> <map:when test="luceneparse">
> <map:generate src="views/luceneparseerror.xml"/>
> <map:serialize type="html"/>
> </map:when>
> </map:select>
> </map:handle-errors>
>
> </map:pipelines>
>
> </map:sitemap>
>
>
> hth,
> Frank
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
