> The fbjava documentation specifically says not to put more jar files there: > > """ > The internal classes necessary for FB/Java are in > <fbjava-root>/jar/*.jar > and is not recommended to put more jar files there. > """
"Not recommended" does not mean "must not" or "is not supported" > """ > It is general recommendation that users store they classes in the database > """ > > The documentation does seem to hint that it might be possible (and the code > seems to confirm that), but given it is not recommended, I wouldn't do it. We just want to know how to make it work -- recommendations notwithstanding. > Looking at the code involved, deploying this way will probably require a > restart of Firebird for each change (but my knowledge of C++ and Firebird > plugins is limited). I'm not sure if that is desirable. Again, you/the developer would have the choice of deployment approach. But for many groups making schema changes (which a new version of a plug-ins would be equiv to) is not something that is done on a live/active database. For ourselves, we make full copies of all databases prior to applying changes, to ensure that if there is some problem in the upgrade deployment, we can roll back without issue. Sean ------------------------------------------------------------------------------ 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
