tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martijn Brinkers (JIRA)" <...@tapestry.apache.org>
Subject [jira] Commented: (TAPESTRY-2533) Only one decorateRequestExceptionHandler is used even though I have defined more than one
Date Thu, 24 Jul 2008 14:25:31 GMT

    [ https://issues.apache.org/jira/browse/TAPESTRY-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616488#action_12616488

Martijn Brinkers commented on TAPESTRY-2533:

In the log I get the following

[23 Jul 2008 22:34:20 btpool0-1] WARN  Could not add object with duplicate id 'RequestExceptionHandler'.
 The duplicate object has been ignored.    (org.apache.tapestry5.services.TapestryModule.RequestExceptionHandler)

But I do not add a 'RequestExceptionHandler' I just decorate it

> Only one decorateRequestExceptionHandler is used even though I have defined more than
> -----------------------------------------------------------------------------------------
>                 Key: TAPESTRY-2533
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2533
>             Project: Tapestry
>          Issue Type: Bug
>    Affects Versions: 5.0.13
>            Reporter: Martijn Brinkers
> I have two submodules and in each submodule I have defined a
> decorateRequestExceptionHandler. The problem is that only one is used.
> For only the first submodule that defines the
> decorateRequestExceptionHandler method the decorate method is called. If
> I add decorateRequestExceptionHandler to the 'main' module only the
> decorateRequestExceptionHandler method of the main module is called.
> I thought it was possible to have multiple decorators for the same
> service. From the Tapestry docs "It is also common to have multiple
> decorations on a single service. In this case, a whole stack of
> interceptor objects will be created, each delegating to the next.
> Tapestry IoC provides control over the order in which such decorations
> occur."

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message