i made my own java.sql package and added No-Op interfaces and classe representing SQLClientInfoException, NClob, SQLXML. My code compiles fine, but if we add this package to openejb code, would that be a violation of some kind of java license
In terms of a proxy, wouldnt you still need the interfaces for the proxy to implement, unless you are talking about different proxies for different versions of jdk resolved at runtime. Is that what you mean by dynamic proxy in this scenario? On 1/23/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
On Jan 22, 2007, at 8:42 PM, David Blevins wrote: > > On Jan 6, 2007, at 5:50 AM, Karan Malhi wrote: > >> This is the first time i have noticed it. I dont know what other >> projects >> do, but i think we could simply provide empty implementations of the >> inherited abstract methods. I can provide a quick patch for this. >> The JIRA >> issue is OPENEJB-435 > > I gave this patch a shot and it fails to compile in JDK 1.5 as > these classes don't exist: > > import java.sql.NClob; > import java.sql.SQLClientInfoException; > import java.sql.SQLXML; > > Does anyone know if there are many backport versions of these that > we could use or some way to support 1.6 without breaking 1.5 support? Alternatively, we could use a dynamic proxy. That would have the added benefit of being able to expose the vendor specific interfaces in addition to all new jdbc stuff as it is added. -dain
-- Karan Malhi
