Winston:
> Hello. I am having trouble understanding the instructions in the
> documentation for using the extension modules
> (
http://exist.sourceforge.net/extensions.html). I am using eXist version
> 1.1.1. deployed in Tomcat via the .war file.
I use a similar setup, just with the latest SVN source build.
> I would like to use HTTP Module, the Date and Time Module, and the Image
> Module (all created by Adam Retter). In the documentation, it says "The
> source code for extension modules should be placed in their own folder
> inside $EXIST_HOME/extensions/modules/src/org/exist/xquery/modules" but I have
> no 'extensions' directory in my eXist home directory. The closest thing I can
> find is $EXIST_HOME/api/org/exist
>
> Also the documentation says "They may then be compiled in place using
> either $EXIST_HOME/build.sh extension-modules or %EXIST_HOME%\build.bat
> extension-modules depending on the platform.", but I do not have a
> build.sh file or a build.bat anywhere. Even if I did have those files, I am
> still not clear on how to "compile in place".
These instructions are more for creating your own custom extension modules,
than for using the existing ones that come with the distribution.
> Could someone help me with step-by-step instructions on how to get these
> modules working?
Just go into your conf.xml file. found in the war file in the WEB-INF dir (or
conf.xml.tmpl if you are building from source), go near the bottom of the
file, and look for the comment Optional Modules. Uncomment the ones that you
want to use.
Once you do this, and redeploy your app, you'll have these modules available
for use, and the xquery functions they provide will appear in the function
documentation page (accessible from the main exist page on your server).
I think the existing modules are all included in the distribution, and you
won't need to rebuild from source, just uncomment and redeploy.
You might also be interested that I've just started working on the HTTP
module and am planning to add PUT, DELETE, HEAD and OPTIONS methods, along
with a mechanism to get the server HTTP status code and headers back along
with the HTTP response body. It'll be a bit before this is done, so watch
for it in days/weeks to come. I'll try to remember to post to the list when
it's call coded, tested and checked into the SVN repository.
Hope this helps...
Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>
http://get.splunk.com/_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open
