Hello!
Can anyone think of an *elegant* way how to change the T5 loggers to include
some per request information (e.g. sessionid, or request.getRemoteAddress()
or something similar) in order to provide better traceability of webapp
events? Seems like a common problem.
I am not an expert on
The best way to do it is with slf4j MDC class probably. Sorry, forget the
question, it is not Tapestry related. It can be done elegantly with logging
framework.
karu3 wrote:
Hello!
Can anyone think of an *elegant* way how to change the T5 loggers to
include some per request information
Hello!
I am browsing the T5 API and somehow do not understand how is it possible to
get all (e.g. defined in a template) embedded component ids for a given
component.
There is ComponentResources.getComponentModel().getEmbeddedComponentIds()
but it returns only those embedded component ids that