Yep, doing something like that. Here is the package in the code that implements
the bridge:
https://github.com/bootique/bootique-tapestry/tree/master/src/main/java/io/bootique/tapestry/di
Comments, suggestions and pull requests are welcome.
Andrus
> On Dec 19, 2016, at 8:19 PM, Thiago H. de Pa
Hi!
Maybe you could try contributing an ObjectProvider to MasterObjectProvider
if you haven't done so yet (I'm sorry, I'm curious to see your Guice to
Tapestry-IoC implementation, but I haven't had the time to do it yet).
On Fri, Dec 16, 2016 at 5:12 AM, Andrus Adamchik
wrote:
> > I haven't fou
> 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
Hi!
On Tue, Dec 13, 2016 at 5:31 AM, Andrus Adamchik
wrote:
> From what I gather Tapestry 5.4 still does not support parameterized
> service injection?
It does not. I haven't found yet a situation in which I wanted something
like that. I've see people creating a MyServiceSource service, for ex
