As part of my work for DERBY-688 I've made some slight changes to the XML
operators that were added in DERBY-334 and I've also added a new operator, XMLQUERY.
These operators depend on the presence of classes that are technically
external to Derby. Or more specifically, they expect that the
Army wrote:
As part of my work for DERBY-688 I've made some slight changes to the
XML operators that were added in DERBY-334 and I've also added a new
operator, XMLQUERY.
[snip]
While this works, I can't help but wonder if Derby has some sort of
existing mechanism/utilities to check for the
Daniel John Debrunner wrote:
Derby's loading of modules from modules.properties has a mechanism where
a module is not loaded if its declared list of classes are not loadable.
snip
Otherwise the utility class
org.apache.derby.iapi.services.loader.ClassInspector has some methods,
you could
