Database Reference
In-Depth Information
We create a new variable by instantiating an instance of org.exist.xquery.Vari
ableImpl .
The variable must, of course, be named, but that name must reside within the
namespace of the internal module.
We set the value of the variable.
We declare the variable within the internal module.
We again create a variable, set its value, and declare it.
Module Configuration
You have probably noticed by now the parameters argument that is given to your
internal module class's constructor. So far we have largely ignored this, and we sim‐
ply pass it on to the super class's constructor as required. When you configure eXist
to use your internal module in $EXIST_HOME/conf.xml , you can also specify config‐
uration parameters inside the module declaration, and these parameters will be
parsed, extracted, and passed in the parameters argument of your module's con‐
structor.
This is a rather simple configuration facility, and is the same used elsewhere for
scheduled tasks (see “Java Jobs” on page 441 , “Startup Triggers” on page 446 , and
“Java Triggers” on page 457 ). As well as those other mechanisms, which share the
same configuration semantics, the xslfo module (see xslfo ) makes use of such
parameters and serves well as an example of how to do this for your own internal
modules.
Developing eXist
The eXist development community is always open to new contributors, beginners or
experts, from those who just want to fix a typo in the documentation to those who
want to reengineer the core storage of the database. Whatever your level of expertise,
all contributions are treated equally and follow the same process to reach acceptance.
eXist makes use of the fork and pull GitHub model of collaborative development .
Simply put, all contributors follow the same three steps:
1. Fork the eXist Git repository that you are interested in contributing to from
https://github.com/eXist-db to your own GitHub user/organization.
2. Make your changes within your fork (preferably using git-flow ) .
If you are modifying Java code, you must run eXist's test suite (see the test entry
in Table 16-9 ) and check that there are no regressions.
Search WWH ::




Custom Search