> transactionhandler.xml
[snip]
Why did you not simply remove it?
I was not sure what to do. It depends on what we want with the applications in the distribution. There are two options.
The application XML Importer is part of the 1.7 release, because it's JSP's are present in /mmbase/xmlimporter and it's classes in mmbase.jar. But unlike for example the application Community, is it's configuration file not present (/WEB-INF/config/modules/transactionhandler.xml) and not switched to active. Community (/WEB-INF/config/modules/communityprc.xml) is present and is active but it is missing its builders cause it's application was not set on auto-deploy.
1. Make these applications fully active on the first start of the release (setting module configuration files on active and applications on auto-deploy). That means that for example the community application will load and try to install it's builders.
2. Put all the needed files for these applications in their appropiate configuration directories but make them inactive. Their JSP's, the documentation and the readme's in the release should point users to the configuration files to activate the applications.
I am in favor of the second one.
---Andr� --
------------------------------------------------------------------>><<-- Andr� van Toly web http://www.toly.nl telefoon 06-27233562
