You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/05/03 10:53:15 UTC
[jira] [Commented] (TAP5-2262) IOC bind method does not allow
specification of multiple markers
[ https://issues.apache.org/jira/browse/TAP5-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988622#comment-13988622 ]
ASF subversion and git services commented on TAP5-2262:
-------------------------------------------------------
Commit 4ca5ff117597b2dbe06fea9edb5bfc7acaea80c0 in tapestry-5's branch refs/heads/master from [~jkemnade]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=4ca5ff1 ]
TAP5-2262: Change org.apache.tapestry5.ioc.ServiceBindingOptions.withMarker() signature to allow for the specification of multiple different marker annotations
> IOC bind method does not allow specification of multiple markers
> ----------------------------------------------------------------
>
> Key: TAP5-2262
> URL: https://issues.apache.org/jira/browse/TAP5-2262
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.4
> Reporter: Adriaan Joubert
> Assignee: Jochen Kemnade
> Labels: easyfix
> Fix For: 5.4
>
>
> When binding a service in an AppModule in the bind() method, the ServiceBinder.bind() method returns a ServiceBindingOptions instance that defines
> <T extends Annotation> ServiceBindingOptions withMarker(Class<T>... marker);
> But this does not allow adding more than one marker, as they never have the same Class<T>. Modifying this to Class<? extends Annotation> would solve the problem.
> Thanks,
> Adriaan
--
This message was sent by Atlassian JIRA
(v6.2#6252)