> I haven't found yet a situation in which I wanted something
> like that.
> I've see people creating a MyServiceSource service, for example,
> which then provides the type-specific services, though. I'm more of a fan
> of having specific subclasses or implementations for each type in most
> cases.
Ah, good point. This might work. Let me see if I can properly bridge / generate
service IDs from Guice to Tapestry.
Thanks,
Andrus
> On Dec 15, 2016, at 8:04 PM, Lance Java wrote:
>
> You should be able to use @InjectService assuming each has a unique id.
>
> @InjectService("s1")
> private
You should be able to use @InjectService assuming each has a unique id.
@InjectService("s1")
private MyService s1;
@InjectService("s2")
private MyService s2;
On 13 Dec 2016 7:31 a.m., "Andrus Adamchik" wrote:
> From what I gather Tapestry 5.4 still does not support parameterized
> se