so your websocket clients can connect to the broker via the broker's WS transport connector. WS is not a client transport to be used in java code. take a look at jetty's websocket impl for the client side (or some other imp) if you want to use websockets as the transport from a java client. however, what's the reason to do this? just use tcp for the java client to connect to the broker. the web-based clients can use WS.
On Fri, Feb 28, 2014 at 3:57 AM, mcJony <sauron1...@yahoo.es> wrote: > I was debugging. I generated the war and I deployed it in the tomcat7 server > but the exception is thrown too. > > The broker is listenint ws and tcp transport. I tried to change the url > connection using tcp instead ws and it works, but when I use the ws > transport the exception is thrown. > > I'm using activemq 5.6.0 original libraries, inluding in the war (and in the > eclipse porject too) these libraries: > > activemq-all-5.6.0.jar > /lib/optional/activemq-optional-5.6.0.jar > /lib/optional/commons-httpclient-3.1.jar > /lib/optional/jetty-6.1.26.jar > /lib/optional/jetty-util-6.1.26.jar > /lib/optional/xstream-1.4.2.jar > /lib/activemq-web-5.6.0.jar > /lib/web/jetty-all-server-7.6.1.v20120215.jar > /lib/web/jetty-websocket-7.6.1.v20120215.jar > xstream-1.3.jar > xpp3_min-1.1.4c.jar > > Need I some other libraries? > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Could-not-create-Transport-Reason-java-io-IOException-createTransport-method-not-implemented-tp4678384p4678410.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- Christian Posta http://www.christianposta.com/blog twitter: @christianposta
