> > I'm leaning towards a custom implementation of > > ComponentEventLinkEncoder (possibly extending the internal T5.1 impl) > since the URL analysis which is going on in here is what I need to > figure out what (if > > anything) needs doing to the URL. > > As Fernando Padilla would point out and I would agree 100% :), > decorating services is almost always a good option. In this specific > case, you would need to change the Link instances returned by > ComponentEventLink methods, something that the URL rewriting support > already does.
I can see how that would work, but as I said I'd be repeating a fair bit of the URL analysis that the ComponentEventLinkEncoder is already doing which is why I'm not planning to decorate, advise or rewrite for my use case. Thanks for the help anyway Thiago. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
