>> BTW, do you have Java-plugin implemented ? If yes, does it requires Jaybird (or
>> another Java connectivity driver) support as original plugin did ?
>>
> Well, since original implementors doesn't showed the Java code :-), I
> had need to start things. And I started yesterday. I never wrote JNI
> code before, but I'm already able to load JVM, pass control to Java for
> functions, and access others (not the "current" attachment/transaction)
> databases using Jaybird with very small changes. Things are very basic yet.

Hmmmm... I am pretty surprised that you did not even send an email about
what you were up to... considering that Vlad has a version of that
plugin, I have two of them, you could save some time. On the other hand,
you know how to code JNI now :)

> Yes, it requires Jaybird and don't think we should do other thing. I
> started things on firebird2 tree but I'll move (offline for now) to
> client-java tree.

May I ask you to show me the parts for review before you commit them?

> Do things on firebird2 tree looks attractive due to
> C++ class library and build things direct. But it will anyway requires
> Jaybird, and it will requires some changes on it. Also not many things
> of our class library will be needed on the Java plugin.

I think the client-java (or even new module) is the right place for such
code, not Firebird itself. I would vote for a separate module
considering that I still want client-java to be splitted in multiple
submodules anyway to have better dependency tracking.

Roman