Craig McClanahan wrote:
> As Sam points out, the incompatibility in the JDBC APIs was raised
> during 1.4 development, but fell on deaf ears at the time.
>
> For a technical workaround, you might want to take a look at the kludge
> adopted by the DBCP package in jakarta-commons -- in essence, we
> simulated an #ifdef/#endif structure by using Ant filtering to remove
> some comment markers on a 1.4 system, but left the new methods commented
> out otherwise. In testing so far, it appears that you still get
> portability both directions if you're not using the new methods.
> However, you'd want to make sure that release builds of Cocoon are
> compiled with 1.4.
>
> Craig McClanahan
Ummm, and the classes output as JDK 1.2 compatible. I made the mistake
of releasing Avalon compiled on JDK 1.4--the class format has
sufficiently changed that at runtime, the classes will not work with
other classes compiled in a prior JDK. By adding the flag to javac
that lets the class files be JDK 1.2 compatible, we had the benefit
of the new JDBC compatibility and the ability to run it with classes
compiled for older JVMs.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
