[Exist-open] Specifying extension modules in conf.xml

[Mark C. <co...@ma...>]

My understanding is that the builtin-modules section of the conf.xml is to
allow enabling/disabling of modules that can be found in exist-modules.jar.
So, if we want to disable the FileModule we just make sure it is
commented-out.

Is this correct?

However, from what I've seen so far, even if a module is not specified in
conf.xml, it can still be used by including the relevant import module
statement in the xquery. Specifying the module in conf.xml seems to allow us
to avoid explicitly importing the module for each xquery.

If this is true, then the only way to disable a module completely would be
to remove it from that jar file?
-- 
View this message in context: http://www.nabble.com/Specifying-extension-modules-in-conf.xml-tp21432614p21432614.html
Sent from the exist-open mailing list archive at Nabble.com.