[
https://issues.apache.org/jira/browse/TAP5-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade closed TAP5-2195.
--------------------------------
Resolution: Invalid
{{Advise.id}} is the advice's ID, not the service ID. To match specific
services, you'll need to use combine {{@Advise}} with {{@Match}} or other
marker annotations. See http://tapestry.apache.org/service-advisors.html
> @Advise is ignoring id when serviceInterface is set
> ---------------------------------------------------
>
> Key: TAP5-2195
> URL: https://issues.apache.org/jira/browse/TAP5-2195
> Project: Tapestry 5
> Issue Type: Bug
> Affects Versions: 5.3.7
> Reporter: Alessio Gambi
> Priority: Minor
> Labels: Advise
>
> It seems that the code handling @Advise is ignoring id when serviceInterface
> is set. I think Tapestry-IoC shouldn't let both attributes (id and
> serviceInterface) to be used at the same time, as service id always subsumes
> serviceinterface.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
