I finally came up with a solution: instead of require the Request service inside the contribute method or in the Module, I defined a BaseURLSource service and declared it in the bind method. Then, on the contribute method I receive this new service (which has a specific id in order to coexist with the default BaseURLSource service) and make the contribution to the configuration. This way, there is no recursion. I suppose this is because of the proxies (before, I had the overriding implementation as an anonymous class inside the contribute method…).
But still, it would be nice to know if it is really not possible to require Request service in a serviceOverride or Alias contribution or if I was doing something wrong. Regards, Raul. -- View this message in context: http://tapestry-users.832.n2.nabble.com/Is-it-possible-to-override-a-service-if-I-need-Request-service-in-order-to-do-it-tp5437958p5438026.html Sent from the Tapestry Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
