Jukka Zitting ha scritto: > Hi, > > On 5/24/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote: >> Please note that JAMES will not build with Java 6 unless Mordred is >> removed >> or updated. Incompatible changes in JDBC. > > I checked that and the problem is > org.apache.james.util.mordred.PoolConnEntry class that implements > java.sql.Connection. Just adding dummy placeholders for the new > methods in JDBC 4 doesn't solve the problem due to a reference to the > new SQLXML interface. > > How about using commons-dbcp for that functionality? The > o.a.j.util.mordred.JdbcDataSource class could even be kept as a facade > for commons-dbcp for full backwards compatibility with existing > configurations.
IMO in trunk we can even remove mordred at all. It is deprecated stuff. In our config.xml we wrote this since at least JAMES Server 2.2.0 (meaning 3 years ago): "James has previously used an in-house connection pool, Mordred. Mordred is being deprecated in favor of Jakarta Commons DBCP." I'm +1 to remove mordred at all in trunk (after tagging because before this change trunk is backward compatible to 2.3.1, instead after this change we are no more 100% compatible). Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
