Hi,
Am 07.09.2015 um 16:44 schrieb Thiago H de Paula Figueiredo:
But this will only help if you can change the source of the module
where the service is *created*. ;-)
I'm not claiming otherwise. ;) My plan is exactly about the need to be
explicit to define a default service implementation.
Well, I still don't think that there will be much benefit if we add this
behavior, but if you think so, let's do it. If it causes trouble, we can
still remove it before 5.4 final.
I'm not sure we can define services which will be used in the code that
handles services themselves.
I'm not sure either, it was just something that came to my mind to be
able to handle all the use cases. But maybe that's more that we actually
want to be able to handle anyway.
For me, if there's more than one service implementation of the same
service with @Default(ServiceImplemenation), it's an outright fatal
exception because it's not possible to know with 100% certainty what's
the default one because we have two.
Yes, that's why I proposed the default implementation should fail in
that case. ;-)
Jochen
On Tue, 25 Aug 2015 10:15:45 -0300, Nathan Quirynen (JIRA)
<j...@apache.org> wrote:
Nathan Quirynen created TAP5-2491:
-------------------------------------
Summary: Default marker annotation
Key: TAP5-2491
URL:
https://issues.apache.org/jira/browse/TAP5-2491
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.3.7
Reporter: Nathan Quirynen
Priority: Minor
It would be nice when making use of Marker annotations for
tagging a
service, that a default marker value could be defined. So when no
marker annotation is added to the injection of the service this
defined default will be used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
