[
https://issues.apache.org/jira/browse/JCR-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581918#action_12581918
]
Marcel Reutegger commented on JCR-1462:
---------------------------------------
I'm not happy with the current situation. Now that validation is enabled, there
is a warn message in the log for every workspace.xml file we have. I'm not sure
what causes it, but it's probably the missing DTD in the workspace.xml files.
I'd rather want to see the initial idea implemented that the repository does
not start up when there is an unknown parameter in the configuration. XML
validation is IMO worth a different discussion.
> repository.xml: throw an exception on error
> -------------------------------------------
>
> Key: JCR-1462
> URL: https://issues.apache.org/jira/browse/JCR-1462
> Project: Jackrabbit
> Issue Type: New Feature
> Components: jackrabbit-core
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Minor
> Fix For: 1.5
>
>
> Currently, unsupported parameters in repository.xml and workspace.xml are
> ignored.
> To find problems earlier, such problems should result in an exception,
> and starting such a repository should not be possible.
> The same should happen for unsupported values.
> For currently unavailable options
> (such as text extraction filter classes if the class is not in the classpath),
> at least a warning should be written to the error log, or an error should be
> thrown.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
