The stack trace reported is...
java.sql.SQLException: [JDBC Progress Driver]:-20217
at
com.progress.sql.jdbc.JdbcProgressConnection.prepareStatement(JdbcProgressConnection.java:518)
at
com.progress.sql.jdbc.JdbcProgressConnection.prepareStatement(JdbcProgressConnection.java:466)
at
cirrus.hiber
> [snip] We'd
> prefer not to have to use some other logging mechanism, so of course it
> would be nice (but not essential) if we could supply a custom log object
> which exposed logging interface(s) for Hibernate to use, so events would
be
> logged within our own system.
>
>I haven't used log4j,
Does Phillip or anyone else who has used Progress does have any idea about
this problem:
http://sourceforge.net/tracker/index.php?func=detail&aid=545543&group_id=40712&atid=428708
I will try to replicate the bug sometime in the next couple of days, but
perhaps there is a simple solution
Tha
> Someone else suggested we use the apache commons logging framework which
> basically just abstracts log4j, jdk 1.4 logging and potentially any other
> logging infrastructure you might want to use.
I took a look at the Apache commons logging docs
(http://jakarta.apache.org/commons/logging/api/ind
> would there be any advantage in having a "proper"
> approach to logging events inside the persistence layer? (Beyond the
> present rudimentary approach of System.out.println() when
> hibernate.debug>0) We could pretty quickly rip out all the printlns and
> replace them with log4j, for example. Bu
