You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Martijn Brinkers (JIRA)" <de...@tapestry.apache.org> on 2008/07/24 18:35:32 UTC
[jira] Updated: (TAPESTRY-2533) Only one
decorateRequestExceptionHandler is used even though I have defined more
than one
[ https://issues.apache.org/jira/browse/TAPESTRY-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martijn Brinkers updated TAPESTRY-2533:
---------------------------------------
Attachment: decorateDemo.tar.gz
Demo project attached showing that only the first decorateRequestExceptionHandler (defined in AppModule) is used. The second decorateRequestExceptionHandler defined in the second module (SecondModule) is not activated.
If the decorateRequestExceptionHandler is removed from AppModule the second decorateRequestExceptionHandler is used.
> Only one decorateRequestExceptionHandler is used even though I have defined more than one
> -----------------------------------------------------------------------------------------
>
> 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
> Attachments: decorateDemo.tar.gz
>
>
> 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