[
https://issues.apache.org/jira/browse/MYFACES-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070759#comment-13070759
]
Martin Kočí commented on MYFACES-3235:
--------------------------------------
a little background for this issue.
- for those who think that logging does not need to be improved:
Please create a facelets view with at least 100 component. Then ask your
collegue to change one id to <component id=""> (empty String) and do not look.
Then try to solve this issue without debbuger.
or: Try to solve random viewExpiredException in production server without
debugger.
or: try to set OFF logging of AbortProcessingException in both places without
grepping myfaces code
Example from real world: I work with tens developers, many of them work in
restricted area on military software. There is no Internet, no possibillty to
attach debbuger to servers and what you want use internet, you must go in
other building and pass security control (and undergo humiliatory personal
examination ;). Now there are problems: how can they solve issue with myfaces?
Athough they can use debugger on local stations, they can run only one
subsystem and probably not every developer will understand myfaces code -
furthermore the developed system is so complex that issue is often reproducible
only in final build of system (4GB distribution binary) and that is not runable
on stations :). The only help that I can give them is "use logging". But I
detected following problems:
1) there are no easy names for myfaces loggers, there is no easy way for
myfaces users to turn on logging for specific myfaces subsystem/logical area
2) message are not trivially identifiable
3) message often does not help to solve problem
ad 1) create logical names for logger
ad 2) identify each log mesage/exception message with code MYFACES-number
ad 3) use this structure in myfaces code, remove useless logs like "entering
method" and replace with something useful that can help solve problem
And that's all. Any suggestion are welcomed. Do you have similar problem as I
do? How do you propose to solve it?
> Create infrastructure for improved logging
> -------------------------------------------
>
> Key: MYFACES-3235
> URL: https://issues.apache.org/jira/browse/MYFACES-3235
> Project: MyFaces Core
> Issue Type: Sub-task
> Components: General
> Reporter: Martin Kočí
> Assignee: Martin Kočí
> Priority: Minor
> Attachments: MYFACES-3235.patch
>
>
> Create classes like MyfacesLogger, MyfacesLogRecord etc. like Trinidad has.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
