I don't know Thiago, I suppose that may be true, but I never tried it... In theory, the only thing you really need is a reference to the Tapestry registry in order to publish the endpoints, this was the best solution I found at the time, I am still not convinced I would do it any other way.
----- Original Message ----- From: "Thiago H. de Paula Figueiredo" <thiag...@gmail.com> To: "Tapestry users" <users@tapestry.apache.org> Sent: Wednesday, 5 October, 2011 14:41:16 GMT +02:00 Athens, Bucharest, Istanbul Subject: Re: T5.2 and Metro / SOAP On Wed, 05 Oct 2011 08:03:50 -0300, <p.stavrini...@albourne.com> wrote: > Hello! Hi! I haven't tried what you've done, but I don't think you need to subclass TapestryFilter. Couldn't the logic inside publicEndpointSingletonServices be replaced by a class contributed to the RegistryStartup service? I can't see anything that needs to be in a servlet filter. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br --------------------------------------------------------------------- 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
