Thanks very much for the help, guys! I successfully employed the approach
detailed by Thiago, with a little extra finessing from the man himself, and
it's working exactly the way I want.
John
On Sat, Dec 7, 2013 at 8:22 AM, Thiago H de Paula Figueiredo
thiag...@gmail.com wrote:
On Fri, 06
Since you want two services which implement FooProvider you'll need to
disambiguate either by serviceId or by marker annotation. See here for info
http://tapestry.apache.org/defining-tapestry-ioc-services.html
Another solution is to instead use 2 service interfaces (FooProvider and
FooOverrides).
On Fri, 06 Dec 2013 22:57:14 -0200, John Prestel
jpres...@safaribooksonline.com wrote:
I'm building a service MasterFooProvider that takes contributions of type
FooProvider. I'd really love for one my FooProvider implementations,
ConfigurableFooProvider, to be able to take contributions of
I'm building a service MasterFooProvider that takes contributions of type
FooProvider. I'd really love for one my FooProvider implementations,
ConfigurableFooProvider, to be able to take contributions of its own (of
type String), so its behavior can be customized.
My first stab at implementing
