>> 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.
>
> In the Java code, I expect small additions (new GDS Plugin), and maybe
> some small changes. I want to develop in the same tree because it will
> be easier.

Ok. This can be splitted later if needed.

I mean, when we think of the complete support (different ideas were
discussed a lot of times like automatic loading classes from BLOBs,
maybe some management interface, maybe even some kind of isql in Java
that allows specifying Java code inside an .sql script, etc.) it must be
separated from the JDBC driver.

> For the C++ code, it may be inside or outside jaybird dll/so.

One library is always better than two :) In my version I have the code
separate from jaybird.dll. In fact those are three projects: main JNI
stuff as statically linkable library, one project producing jaybird.dll
and one producing javaesp.dll. From my POV this provides good
modularisation with reasonable maintanence efforts.

Roman