Yoav,
I don't think that would work because more/all of the data fields
of interest are private or package.
--- thanks ---
Larry
At 08:47 AM 9/4/03 -0400, you wrote:
Howdy,
I personally am not a big fan of logging these types of objects: I much
prefer logging the beans I create from
Don,
Yes, I had considered that, but most/all of the interesting data
inside most PreparedStatment classes (DB2 AS400 JDBC classes in
particular) is non-public, so introspection wouldn't touch it unless you
toyed with the SecurityManager stuff. The other problem is that most of
Kevin,
That is exactly what I was thinking of. Thanks for the code, I
just briefly looked at it and it appears to be pretty close what I had in
mind. After a quick look, the only change that I will probably make is
that I will create mine as a wrapper instead of a subclass, and take
Howdy,
I personally am not a big fan of logging these types of objects: I much
prefer logging the beans I create from result sets (or DAO objects, or
whatever we call them this week). However, one possibility for you
would be to create a ResultSetRenderer (implements
Howdy,
At my company, I am in our production support team and I can say that it is
VERY helpful to log PreparedStatements with the parameters replaced. This
makes it very easy to debug problems with SQL in code. I have attached my
wrapper PreparedStatement class. Hopefully this helps.
Kevin
In the past I have used a generic bean-util style widget that uses
reflection to introspect any passed Object, and dumps its contents into a
formatted Stringwhich is then in turn logged.
The DumpUtil (as I have implemented anyway) works well for reasonably
simple/flat Objects, but does not
AM
To: Log4J Users List
Subject: RE: logging JDBC objects
In the past I have used a generic bean-util style widget that uses
reflection to introspect any passed Object, and dumps its contents into
a
formatted Stringwhich is then in turn logged.
The DumpUtil (as I have implemented anyway) works
: Thursday, September 04, 2003 10:02 AM
To: Log4J Users List
Subject: RE: logging JDBC objects
In the past I have used a generic bean-util style widget that uses
reflection to introspect any passed Object, and dumps its contents into
a
formatted Stringwhich is then in turn logged.
The DumpUtil
