On 16-5-2018 16:47, Chmakov, Vladimir wrote:
Hello Mark,
Thank you for your reply!
Yes, the documentation recommends placing JARs inside the DB, but the
"external" deployment better suits our software deployment policies.
My expectation would be that regardless of the JAR deployment model all JAR components
exposed onto the class path would be visible for the plugin. It doesn't seem to be the
case, as in the provided example it is obvious, that logback.xml is being ignored or not
visible when JAR deployed "externally".
Could you please describe the exact layout of your deployment, which
files are where? eg: is that logback.xml in a jar file in the
<fbjava-root>/jar/ directory, or did you deploy it separately (which is
not going to work)?
We also tried to push our own JARs into the DB, but ended up getting tons of "PK
violation" errors.
Please describe in more detail what you did and what error you get.
The fbjava plugin probably hasn't seen a lot of use, so unless you
describe exactly what you did, it will be harder to replicate what you
did and either point out what you did wrong, or what is wrong with the
current plugin so it can be fixed.
Mark
--
Mark Rotteveel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
