[jira] Closed: (TAPESTRY-2533) Only one decorateRequestExceptionHandler is used even though I have defined more than one

["Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>]

     [ https://issues.apache.org/jira/browse/TAPESTRY-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAPESTRY-2533.
------------------------------------------

    Resolution: Invalid
      Assignee: Howard M. Lewis Ship

Service decorators are ordered objects; as with an OrderedConfiguration, the decorators have unique ids (the part of the method name after "decorate") and can have ordering constraints ("before:" and "after:", added via a method annotation).  What's happened here is that two different modules have defined a decorator with the same id, causing a failure when the decorators are shuffled into order of application. Modifying the method names will resolve your problem.  You'll then want to use @Match annotation t control what service(s) to target.  Without @Match, the decorator id is expected to match the service id.

> 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
>            Assignee: Howard M. Lewis Ship
>         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