If option #1 works, it could be the ideal solution. I've only ever seen WebSocket annotations on a POJO, never an interface. Not to say it can't be done.
I was about to attempt an 'option #3': do away with the custom Configurator (allowing Tomcat to instantiate endpoints), with endpoints getting their dependencies via the RegistryProxy I created, rather than having them injected. I'll try option #1 first. :) Are you seeking new Tapestry committers? Once I have a final working solution, I'm happy to document the Tapestry and WebSocket integration for others, including source code (ServletContextListener, RegistryProxy etc.). Regards, Chris. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
