Hi all,
we implemented a
resource adapter which makes use of
the PrintWriter instance injected to
the managed
connection factory for error
logging/tracing purposes. By searching for a way to
enable/disable
tracing during runtime we found out
that the JCA container of jboss-as-7.1.0.CR1
just injects a
System.out printer during deployment
time. If I this isn't right, please correct me.
The JCA (1.5) spec
says the following:
"An application
server manages the association
of a log writer with a
ManagedConnectionFactory.
When a
ManagedConnectionFactory instance is
created, the log
writer is initially null and logging
is disabled. Associating a log
writer with a
ManagedConnectionFactory instance
enables logging and tracing
for the
ManagedConnectionFactory instance."
This is exactly the
behaviour that we would like to
have :-)
In our opinion it
would be a better idea to write to
a specific JBoss logger rather than to System.out.
I checked out the
sources from github and locally
tested with a PrintWriter wrapper subclass which
prints out to a
org.jboss.logging.Logger instance if
trace is enabled for that particular logger.
It would be also
nice if we could get notified about log
level changes so that we could reset
the
ManagedConnection.logWriter back to null if
tracing gets disabled. If so, the log writer could be
null checked within
the RA implementation so that the
trace code (e.g. message formatting) doesn’t
need to be executed
if trace is disabled…
Is there a kind of
callback mechanism implemented in
jboss logging?
What's your opinion
about a suitable solution? Do you
have any proposals?
Best regards
Christian