Hi Bernard,

I don't know what your app is, but if your clients are required to run JVM
1.1 (as in the default MS JVM with Windows) you may want to consider setting
the program up as a web app.

Then only the JVM on the server is needed by the app, and you can control
which JVM is used on the server. The clients access the app through their
browsers and no JVM is needed at all on the client side unless you use
applets.

If you need to run it as an executable Java app on the client, you can still
use a a web app on the server and use the Java HTTP classes to transfer the
data to and from the server. There again, the JayBird jdbc driver and 1.2
or greater JVM only needs to be on the server.

Rick

----- Original Message -----

> Hi,
>
> > After reading about this error, it appears that it should be possible
> > to compile Jaybird in the latest JDKS using a "target 1.1" parameter.
> >
> > Would this be a total waste of my time (i.e. is there so much later
> > stuff required that it simply will not work)? If not, could anyone
> > point me in the direction of the necessary source code.
> >
> > Regards
> > Bernard.
>
> I think so. Most likely it will not compile. We are using reflection
> in some places, dynamic proxies, etc. You should be able to build
> org.firebirdsql.gds.* and org.firebirdsql.jgds.* classes, but not JCA
> and JDBC classes. So, even if byte code will be 1.1 compliant, it will
> not run in 1.1 JVMs.
>
> Best regards,
> Roman Rokytskyy