Hi Gerald, it accesses /amq but as POST and provides some data, like destination and such. You can also take a look at
https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-web-demo/src/test/java/org/apache/activemq/web/AjaxTest.java?hb=true it should help understand what's happening under the hud. It'd also be good to try verify your js application is working in standalone broker by copying it to webapps/demo folder with properly configured servlet (and feeding it with some mock messages). Hope this helps. Regards -- Dejan Bosanac Senior Software Engineer | FuseSource Corp. dej...@fusesource.com | fusesource.com skype: dejan.bosanac | twitter: @dejanb blog: http://www.nighttale.net ActiveMQ in Action: http://www.manning.com/snyder/ On Tue, Mar 20, 2012 at 3:21 PM, unficyp <gerald.we...@besharp.at> wrote: > I'm currently not at home so i can't try my code. > > I tried the portfolio example coming with the websamples. > portfolio.html first connects to the url http://127.0.0.1:8161/demo/amq > if i point the browser to the same url and start the portfolio publisher, i > get a response back, not only the > empty <ajax-response></ajax-response> > So i'm pretty sure there is a problem with the ajaxservlet. I will > investigate this more when i'm at home. > > thx®ards, > gerald > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Embedded-Broker-AJAXServlet-Jetty-tp4487915p4488964.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
