Tidying up RichFaces logging

[pmuir]

We need to improve what RichFaces logs at what level. JBoss AS appends DEBUG and above to the server.log file, which means that excessive debug output can really slow down your application.

Let's start to collect places at which the logging is too high, or just not useful.

1)

2008-10-21 14:10:02,261 DEBUG [org.ajax4jsf.resource.InternetResourceBuilder] Return instance of internet resource builder org.ajax4jsf.resource.ResourceBuilderImpl@17d4dd

- this one prints out hundreds of times, and contains no useful information

RichFaces logging is just as bad as Seams ;-)

[jbalunas]

There are many other places that have excessive logging as well in RichFaces We need to take a look at what can be moved to "TRACE", and what can be removed.

Such as:

org.ajax4jsf.io.parser.FastHtmlParser] (http-127.0.0.1-8080-1) Parser reached state is StateManager.DOCTYPE

Jay

[sergeysmirnov]

We used to have the clean up task for server side logging in the plan for 3.3.0 (http://www.jboss.org/auth/wiki/RichFacesWhatIsNewIn3_3_0 section 2) before the plan was changed.
I suggest it is still actual and should not be forgotten. Well designed logging (both server and client side) helps to reduce the time developers spend finding problems.