Externalized Configuration about javamelody HOT 3 CLOSED

I am not against this change, but I have 3 questions.

As far as I know, the only way to set a servletContext attribute is to call the 
servletContext.setAttribute(name, value) method, isn't it?
For example, servletContext.setAttribute("javamelody.log", "true")

So, to externalize configuration, you still have to read the names and values 
of parameters from some resource or file, and to call 
servletContext.setAttribute for each one?

And, is there a reason to not use servletContext.setInitParameter(name, value) 
instead?

Yes, that's exactly what I'm doing during context initalization, scan 
configuration params and copy those with "javamelody." to javamelody 
configuration. I'm adding javamelody to existing project, configuration loading 
is already implemented.

My project is build upon gwt, which is still using Servlet 2.5 API 
specification, therefore ServletContext.setInitParameter is not available, 
because it was added only in Servlet 3.0 API specification. 

ok, this is committed in trunk (revision 4043) and ready for the next release 
(1.56).