Changes

Suitable JAR archives may contain one or more class files. One of them will be chosen as main classFor general notes in importing Java classes, which must be specified in a {{Code|Main-Class}} entry in please read the manifest file ({{Code|META-INF/MANIFEST.MF}}). This fully qualified Java class name will be rewritten to a file path by replacing the dots with slashes and attaching the {{CodeBindings article on [[Java Bindings#Module_Imports|.jar}} file suffix, and the original file will be renamed and copied to that path into the repositoryModule Imports]].

The public functions JAR archives may contain one or more class files. One of this them will be chosen as main class can then , which must be addressed from XQuery, using specified in a {{Code|Main-Class}} entry in the manifest file ({{Code|META-INF/MANIFEST.MF}}). This fully qualified Java class or name will be rewritten to a file path as namespace URIby replacing the dots with slashes and attaching the {{Code|.jar}} file suffix, or an alternative writing that can and the original file will be [[#URI Rewriting|rewritten]] renamed and copied to that path into the module file pathrepository. Moreover If the class will be imported, an instance of it will be created, a and its public functions can then be addressed from XQuery. A class may extend the {{Code|QueryModule}} class to get access to the current query context and to be enriched by some helpful annotations (please consult see [[Java_Bindings#Context-Awareness|Context -Awareness of Java Bindings]] for more information).

After having installed the module, all of the following URIs can be used in XQuery to import this module or call its functions(see [[#URI Rewriting|URI Rewriting]] for more information):