Hi, I never tried running ajax through cross domain filter in jetty, but if it creates a new session for every request it surely will be problematic. Is there any way to turn that behavior off?
Regards -- Dejan Bosanac ---------------------- Red Hat, Inc. FuseSource is now part of Red Hat dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Tue, Jan 22, 2013 at 11:22 PM, alaricus <nar...@gmail.com> wrote: > Hi!I've faced some issue. When I run my AJAX-script in AMQ sandbox like > /mysite:8161/myapp/test.html/ all works. But if I run this script from > /mysite2/test.html/ and request /mysite:8161/myapp/amq/ all works but I > don't get any messages. I think that cause is in fact that in the second > case I get new JSESSIONID cookie each request.I attach my sources. > *web.xml* > org.apache.activemq.brokerURL vm://localhost The URL > of the Message Broker to connect to > org.apache.activemq.embeddedBroker true Whether we should > include an embedded broker or not session > org.apache.activemq.web.SessionFilter session > /* cross-origin > org.eclipse.jetty.servlets.CrossOriginFilter > allowedOrigins * > allowedMethods * allowedHeaders > * cross-origin > /* > org.apache.activemq.web.SessionListener > AjaxServlet org.apache.activemq.web.AjaxServlet 1 > AjaxServlet /amq/* > *Page* > test amq > AMQ > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/AJAX-via-crossdomain-tp4662054.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
