Hi Charles, Thanks for launching the idea that we discussed on IRC.
As I said, my point of view is that we need a kind of median console projects for Apache middleware projects. For instance, a lot of stuff is share in all web console of these projects (user authentication, authentication backend, JMX client, etc, etc). By projects, I've identified: Karaf, Felix, ServiceMix, CXF, Camel, Geronimo, (maybe ACE), ActiveMQ, Sling, Tomcat, DS, James, certainly others :). If we can provide a plug and play and branding WebConsole, all these projects can use it. My vision is that we need a generic console (monitoring, management oriented) that could be extended by each project. Depending of the different communities feedback, it could have sense to submit to the incubator mailing list. Maybe we can think about an Apache Operational Network Console (Apache ONC) with plugins provided by the Apache projects.
Regards JB On 03/02/2011 06:37 PM, Charles Moulliard wrote:
Hi, As three users of Apache Felix WebConsole project, I contact you to have your opinion regarding to frameworks (JSon, javascript, ...) usage made with Apache Felix WebConsole. The project has been made light to avoid dependencies with external librairies but the way that it is used today lack of structure, complicate the development of screens and decrease development productivity, html code is mixed in javascript, json variables are set everywhere in the code and use in several of javascript functions, no template is used to render html pages, locale is not used by all of us to translate text, .... The consequence of that is that some developers are very frustrated and would like to make some suggestions about Webconsole. Within Karaf community we already started this discussion and now we would like to share with you some ideas about the future roadmap of Felix WebConsole. Here are the different scenario possible : (1) Improve the existing usage of the frameworks JSon, OSGI and javascript by defining/providing a "template" project containing dummy code + guidelines/best practices to develop properly and so improve/increase productivity. This could be done with an archetype (2) Switch the existing architectural model to use frameworks like Apache Wicket or Vaadin where the content is clearly separated from the server side code. Apache Wicket and Vaadin librairies are already osgified so their integration in project like karaf, sling or felix will be done seamless even if we have the overhead to deploy them. But this is also the same for bundles like PAX-Web, ... No matter which scenario we will decide to adopt, we could also create a project to develop all together the OSGI WebConsole used by our projects and promote it as a new Apache project --> Name suggested Apache Orion. The scope of this project could be extended to include additional management, registration of datasources, .... What do you think my propositions ? Regards, Charles Moulliard Apache Committer Blog : http://cmoulliard.blogspot.com Twitter : http://twitter.com/cmoulliard Linkedin : http://www.linkedin.com/in/charlesmoulliard Skype: cmoulliard
