Re: Publisher - Subscriber pattern for Tapestry Service

On Wed, Jun 21, 2017 at 1:42 AM, abangkis <[email protected]> wrote:

> I was thinking because of how the Services implementation & instantiation
> is managed by tapestry. How the service is injected instead of manually
> created.
>
> Thanks for the hint, I will look at those files source code.
>

There's absolutely nothing special in these classes' sources. They just
receive the observers as their distributed configuration and keep them in a
List or Collection field. But even if you wanted to add or remove observers
on the fly (i.e. after the Registry is started and all services
initialized) that wouldn't be a problem at all.

-- 
Thiago