Hide
original bugid: #6382
The XMLimporter depends on the config/modules/transactionhandler.xml config file which is missing.
The class stated in transactionhandler.xml should be org.mmbase.applications.xmlimporter.TransactionHandler.
The XMLimporter's DTD should be in config/dtd/transactions.dtd, missing also.
The JSP in /mmbase/xmlimporter don't work cause they depend on an import directory that's been read from System.getProperty("mmbase.config") + "/import/" (should be made configurable or something in the JSP's themselves).
The data gets imported in the security context TRaticUser, which in non-existend in this release.
Placed the needed files in their appropiate locations.
Fixed the classname in modules/transactionhandler.xml
Created the ability to specify in the JSP the directory on the server you want to use for your imports.
Will file the security context bug as a new one, so i can close this bug.
Show
original bugid: #6382
The XMLimporter depends on the config/modules/transactionhandler.xml config file which is missing.
The class stated in transactionhandler.xml should be org.mmbase.applications.xmlimporter.TransactionHandler.
The XMLimporter's DTD should be in config/dtd/transactions.dtd, missing also.
The JSP in /mmbase/xmlimporter don't work cause they depend on an import directory that's been read from System.getProperty("mmbase.config") + "/import/" (should be made configurable or something in the JSP's themselves).
The data gets imported in the security context TRaticUser, which in non-existend in this release.
Placed the needed files in their appropiate locations.
Fixed the classname in modules/transactionhandler.xml
Created the ability to specify in the JSP the directory on the server you want to use for your imports.
Will file the security context bug as a new one, so i can close this bug.
Bug
Resolved
Major