There has been a lot of discussion about reworking camel-web with regards to OSGI and multiple contexts. Overall, I agree that this app should be much more comprehensive, extensible and easy to integrate with existing apps. If camel-web can evolve into this...great. But currently, for specific requirements, camel-web is difficult to integrate and customize. I ended up having to build a custom monitoring app for a client recently using HTML, CSS, jQuery, JMX, JSP/Servlets, Google Charts, etc.
Maybe someone from the Fuse team can comment on whether the roadmap for Fuse IDE (or camel-web) overlaps with this effort or not. But I think a new Camel subproject would be a good place to experiment with some alternate approaches for this. Tarun Ramakrishna-2 wrote: > > Hi, > > At a first glance (please correct me if I am wrong), the camel web > console implementation appears to be very heavy - depending on Scala, > scala template engines and several Jersey libraries which have a > non-Apache licenses. It also appears to be unsuited to running on an > OSGi environment where different bundles can contribute camel > contexts. > > Would the committers be interested if someone re-wrote this web-app to > be more simpler (use HTML 5 techniques and move UI logic to client > instead of heavy template engines), remove the Jersey dependencies > (simply use servlets and a plain JSON library or if JAX/WS is really > wanted use CXF for this) and abstract the lookup of Camel Contexts > through some interface? Or is the community more than happy with what > is there now and wouldn't like anything changed ? > > Best Regards, > Tarun > ----- Ben O'Day IT Consultant -http://benoday.blogspot.com -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Web-Console-Questions-tp4425291p4425611.html Sent from the Camel - Users mailing list archive at Nabble.com.
