Вот пример настройки логов для сановской рализации jsf. Для myfaces думаю тоже подойдет.

Logging Support And Configuration Steps
JavaServer Faces Reference Implementation in this release leverages the Jakarta Commons logging API to provide logging functionality. We have followed the guidelines recommended by http://jakarta.apache.org/commons/logging/userguide.html. JavaServer Faces Reference Implementation can be configured to provide logging information using the steps below.

1. If you are using Tomcat or JWSDP as your container, you can set the following property to tell the container what logging implementation you are using as well as the location of your logging configuration file. Set CATALINA_OPTS=-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djava.util.logging.config.file=D:\Files_2k\j2sdk1.4.1_03\jre\lib\jsf-log.properties
2. We have shown a sample logging configuration file below that is configured to get logging output when you are running a JavaServer Faces application. The default JDK 1.4 logging configuration file is "$JAVA_HOME}/jre/lib/logging.properties". You can either manipulate that as per directions below, in which case it's global to all Java apps that you run or you can create a jsf.log properties as illustrated below. You can change the "java.util.logging.FileHandler.pattern" property to control where your logging information is written.

Here's the jsf-log.properties:

############################################################
# Default Logging Configuration File
# http://java.sun.com/j2se/1.4.2/docs/guide/util/logging/overview.html#1.2
# You can use a different file by specifying a filename
# with the java.util.logging.config.file system property.
# For example java -Djava.util.logging.config.file=myfile
############################################################

############################################################
# Global properties
############################################################

# "handlers" specifies a comma separated list of log Handler
# classes. These handlers will be installed during VM startup.
# Note that these classes must be on the system classpath.
# By default we only configure a ConsoleHandler, which will only
# show messages at the INFO and above levels.

# To also add the FileHandler, use the following line instead.
handlers= java.util.logging.FileHandler, java.util.logging.ConsoleHandler

# Default global logging level.
# This specifies which kinds of events are logged across
# all loggers. For any given facility this global level
# can be overriden by a facility specific level
# Note that the ConsoleHandler also has a separate level
# setting to limit messages printed to the console.
#.level= INFO
.level= INFO

############################################################
# Handler specific properties.
# Describes specific configuration info for Handlers.
############################################################

# default file output is in user's home directory.
java.util.logging.FileHandler.pattern = %h/java%u.log
java.util.logging.FileHandler.limit = 50000
java.util.logging.FileHandler.count = 1
java.util.logging.FileHandler.formatter = java.util.logging.XMLFormatter

# Limit the message that are printed on the console to INFO and above.
java.util.logging.ConsoleHandler.level = INFO
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter

############################################################
# Facility specific properties.
# Provides extra control for each logger.
############################################################

# For example, set the com.xyz.foo logger to only log SEVERE
# messages:
com.xyz.foo.level = SEVERE
com.sun.faces.level = ALL

If you use the ConsoleHandler ( which would direct all the output to catalina.out in the case of standalone Tomcat or launcher.server.log in the case of JWSDP ) please make sure that the detail level for ConsoleHandler can handle the level set for individual packages. For example say you have set the level for "com.sun.faces.el" package to "FINEST" as below.
"com.sun.faces.el.level = FINEST"

You won't see any trace or debug messages unless you also set ConsoleHandler.level = FINEST. ConsoleHandler.level caps the detail level to the console, no matter what the underlying loggers are set for.

In this release, the Reference Implementation provides logging support for the following packages.
* com.sun.faces.application
* com.sun.faces.el
* com.sun.faces.lifecycle

The logging messages are not localized. Localization as well as logging for rest of the RI will be done in a future release.

.... Но это не тот случай, тут одни и теже строковые константы хранятся и в файлах настройки и в жава коде. ...

Вот было бы классно, если бы на один и тот же объект, в разных местах указывали бы разные строковые константы. Действительно, как это "дятлы" из сан не додумались так сделать?
Мапинги в JSF, сделаны очень продуманно и удобно, особенно когда их пользуешь в jsf компанентах. Если ты любитель писать <jsp:useBean....> со всеми вытекающими, то флаг тебе в руки.

автор
Да и ещё, чтоб получить параметр из JSP в жава коде нужно использовать такую здоровенную конструкцию:

(TestCase) FacesContext.getCurrentInstance().getExternalContext().getRequestMap().get("testCasesIterator");

куда ето годится.

создай класс с соответствующим полем, опиши класс в faces-config.xml и jsf все само сделает. На худой конец создай класс Utils и в нем статический метод getRequestParam(String name)...

Три вечера знакомства с JSF это конечно большой срок :)) Особенно после нескольких лет работы со Struts. В JSF совсем другая идеология, нужно немного больше времени, чтобы ее понять и осознать.

Сами вы - сырые, некрасивые и нехорошие :)