Re: extension modules must be packaged inexist-modul e.jar?
I have like you built an extension module for eXist. Like you I did it
by starting with the Example module.
I simply used Eclipse IDE to import the code of eXist from CVS. I then
copied the Example extension module and renamed the appropriate files
and class/function names and wrote my code.
The module is now included with eXist, when you compile eXist it will
compile and package my extension module up as part of the build process
and include it in exist-modules.jar.
This way I just need to enable the module in the eXist configuration
file conf.xml, and also the module is there for any other eXist users
should they wish to enable it.
The module I wrote gives eXist the ability to send email's via. Sendmail
or SMTP, feel free to check it out.
Hope that helps...
On Wed, 2005-09-28 at 23:46 +0100, Chris Tomlinson wrote:
> I'm back with another question regarding builtin extension modules.
> It seems that if I'm trying to add the module to a standalone eXist
> installation I seem to have to add the classes to the
> exist-modules.jar. On the other hand sometimes I can just add a
> self-contained xyz.jar to the $TOMCAT_HOME/webapps/exist/WEB-INF/lib;
> except on a linux platform I couldn't get this to work but could get
> it all to work when I rebuilt the exist-modules.jar with my exstenion
> I'd like to do this in the intended way for eXist so I'm looking for
> guidance about what is supposed to be the way to add extension modules
> that will work across the different ways of deploying eXist.
> Please pardon my questions if this has been dealt with in the docs
> already, as I have looked but may have missed the info.
> Thanks in advance,
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads,
> and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________
> Exist-open mailing list
> [hidden email] > https://lists.sourceforge.net/lists/listinfo/exist-open >