In any case I don't think a change like that should hold up a release. Is the release official yet? I'd like to submit the board report and holding off until I find out if this release is the final cut of 5.3
Regards, Hiram On Mon, Oct 12, 2009 at 11:35 AM, Dejan Bosanac <[email protected]> wrote: > Hi, > > demo web app enables REST and Ajax APIs at the moment > camel is the new web console for monitoring camel routes and endpoints. > > I don't see any problem in running these apps by default. > > Cheers > -- > Dejan Bosanac - http://twitter.com/dejanb > > Open Source Integration - http://fusesource.com/ > ActiveMQ in Action - http://www.manning.com/snyder/ > Blog - http://www.nighttale.net > > > On Mon, Oct 12, 2009 at 5:31 PM, Bruce Snyder <[email protected]>wrote: > >> On Mon, Oct 12, 2009 at 9:24 AM, Dejan Bosanac <[email protected]> >> wrote: >> > Hi Bruce, >> > >> > the conclusion was that many people use web console in the production to >> > monitor the broker, so it's there by default. Also, it enables rest and >> ajax >> > apis. >> >> Yes, the /admin app is the web console and I think the /fileserver app >> is the one enables REST. But the /camel and /demo apps are not >> required, are they? Shouldn't those be moved to the activemq-demo.xml >> config? >> >> Bruce >> -- >> perl -e 'print >> unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" >> );' >> >> ActiveMQ in Action: http://bit.ly/2je6cQ >> Blog: http://bruceblog.org/ >> Twitter: http://twitter.com/brucesnyder >> > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://fusesource.com/
