Hi nillehammer, > Isn't this a question of disambiguation of Services either with ids or with > the @Local annotation as described here: > http://tapestry.apache.org/tapestry5.1/tapestry- > ioc/service.html ? Or did I get lost somewhere? I am not sure to be perfectly honest, looking through that link I guess there may have been a case... in my situation Thiagos solution is perfect because I use a generic error handling service that is configured in the shared core module and is reused without change by many applications, but in one particular application I have to extend this service to override some of the handling... so far as I know I could do this either by: - decorating the service - not bind it in the shared core module, and then binding it each applications AppModule (my solution before) - Or implement the override (Thiagos suggestion), which I have now done
But perhaps I could have done it that way as well? regards, Peter ----- Original Message ----- From: "nille hammer" <tapestry.nilleham...@winfonet.eu> To: "Tapestry users" <users@tapestry.apache.org> Sent: Monday, 29 June, 2009 15:31:04 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: Override an IoC service Hi Peter, Isn't this a question of disambiguation of Services either with ids or with t...@local annotation as described here: http://tapestry.apache.org/tapestry5.1/tapestry-ioc/service.html ? Or did I get lost somewhere? Regards, nillehammer == http://www.winfonet.eu ----- original Nachricht -------- Betreff: Override an IoC service Gesendet: Mo, 29. Jun 2009 Von: Peter Stavrinides<p.stavrini...@albourne.com> > Hi, > > I have recently introduced a multiple IoC module structure into my web > applications, so I have a core web module and then application specific > modules separately, and now I am getting the following error: > ERROR - Service interface com.albourne.web.interfaces.ISiteError is matched > by 2 services: CoreError, SiteError. > > I have introduced these changes mostly for testing purposes... its not a big > problem as I can simply remove the offending service from the shared core > and provide an implementation of it in each application specific module, but > it got me wandering about this issue on a larger scale, is it possible to > override a service? if not would such a feature be useful? How do others > deal with this, using service decoration potentially? > > Kind regards, > Peter > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --- original Nachricht Ende ---- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
