Is JDBC 3.0 a JDK 1.4 only feature? Is there going to be an optional pack for 1.3 users? If not, that really sucks. If you want the new drivers, you have to upgrade to a x.0 version VM. Sounds like a M$ move.
BTW, I searched google and couldn't find any info either way. -dain David Jencks wrote: > It turns out there are some problems I didn't anticipate with the new > ConnectionManagers and the non-compliant jdbc wrappers we have, so I went > ahead and wrote a new, jca-compliant, lgpl local-tx wrapper. Since I'm now > developing on jdk 1.4 mostly, I made my new jdbc class wrappers conform to > jdbc 3, delegating all the new sql methods to the driver implementation. > > This wrapper seems to run fine in jdk 1.4 even when it is wrapping a non > jdbc 3 driver. > > Of course, this doesn't compile on 1.3. > > Possible solutions: > > -- get the jdbc 3 classes and compile against them even in jdk 1.3 (Is this > possible??? I don't think you can replace java's built in classes???) > > -- use ant's copy filter to insert /* */ around jdbc 3 code in the > source, compile the copied versions. > > -- throw not supported exceptions like the old wrapper does. (I don't want > to do this, it took a while to write all those wrappers) > > I guess I will try using the ant copy filter -- maybe I can combine the 2nd > and 3rd choices so compiling in 1.3 gives you a not supported exception, in > 1.4 delegates. > > Any advice? > > thanks > david jencks > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
