[
https://issues.jboss.org/browse/SEAMFACES-92?page=com.atlassian.jira.plug...
]
Brian Leathem commented on SEAMFACES-92:
----------------------------------------
This issue was resolved in SEAMFACES-86, which made it in CR1, and confirmed as fixed by
the reporter.
The Catch integration enabled message was changed to level trace.
The "unable to find a BeanManaged instance" was left at warning, but suppressed
for classes that start with "javax."
Are you sure you were running with Seam Faces CR1?
remove excessive log messages
-----------------------------
Key: SEAMFACES-92
URL:
https://issues.jboss.org/browse/SEAMFACES-92
Project: Seam Faces
Issue Type: Bug
Components: Exception Handling, Validation & Conversion
Affects Versions: 3.0.0.CR1
Reporter: Dan Allen
Fix For: 3.0.0.Final
There are currently two logging calls that are producing excessive log messages when
running at the INFO level.
The Catch integration notice is being logged with every request. It should only be logged
once per application.
"INFO [org.jboss.seam.faces.exception.CatchExceptionHandlerFactory] Catch
integration enabled"
The JSF application wrapper is logging at warning level every time a validator is created
using the fallback mechanism. It should be downgraded to a debug message.
"[org.jboss.seam.faces.environment.SeamApplicationWrapper] Using JSF provided
instance, unable to find a BeanManaged instance for class
javax.faces.validator.BeanValidator"
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira