Well TomEE websocket implementation is to write clients from TomEE not from JavaSE (where you don't have TomEE anymore).
In TomEE clients work. So you need to provide us a maven project with a test showing the issue you have. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-05-04 15:20 GMT+02:00 Chuck Davis <[email protected]>: > Niki, I'm not sure what "http proxy setup for client connection" means but > it sounds suspiciously like the very piece I'm looking for -- connecting a > Java client to the server with websocket. Is that what you are saying? > The piece WebsocketContainer container = > ContainerProvider.getWebsocketContainer() will not currently work? > Currently it returns an exception that there is no implementation class. > > If that is so, then my contention stands that Tomee needs a better > implementation to allow Java clients to connect. > > Thanks. > > CD > > > On Sat, May 3, 2014 at 8:24 AM, Niki Dokovski <[email protected]> wrote: > >> The only limitation in Apache Tomcat implementation of Java API for Web >> Socket (JSR 356) is the missing http proxy setup for client connections. >> This has already bean discussed in Tomcat dev lists and so far this is left >> either for future spec definitions or users demand. The rest of the >> implementation is fully functional within the JSR 356 definitions. >> >> Best Regards >> Niki >> >> >> Niki Dokovski | @nickytd >> >>
