[
https://issues.apache.org/jira/browse/JCR-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-695:
------------------------------
Fix Version/s: (was: 1.3)
Priority: Blocker (was: Major)
I noticed this same problem while testing 1.2, it's certainly a blocker.
Using public identifiers with the ConfigurationEntityResolver seems like the
correct solution, but I think we should add a version number to the public
identifier and we probably don't need separate identifiers for the Repository
and Workspace configurations.
Another alternative would simply be to drop the DOCTYPE declarations from the
configuration templates and treat the DTDs as simply manual guidance that you
can use with an XML editor. In any case we don't validate the configuration
files at runtime so having an exact DOCTYPE doesn't bring that much value.
> Repository requires access to external resource
> -----------------------------------------------
>
> Key: JCR-695
> URL: https://issues.apache.org/jira/browse/JCR-695
> Project: Jackrabbit
> Issue Type: Bug
> Components: config
> Environment: Windows XP, Maven 2.0, Java 1.5.0-8
> Reporter: Marcel Reutegger
> Priority: Blocker
> Fix For: 1.2
>
> Attachments: JCR-695-r492185.patch
>
>
> With the changes from JCR-626 jackrabbit requires access to the resource at
> the URL http://jackrabbit.apache.org/dtd/repository-1.2.dtd. If no connection
> to the internet is available jackrabbit will refuse to start. At least that's
> the case when I run the test cases in the above mentioned environment.
> I'm not an XML expert, but shouldn't the doctype declaration use a public
> identifier? Otherwise the ConfigurationEntityResolver class doesn't make much
> sense.
> The attached patch solve the issue for me, please comment. I've also
> targetted this issue for 1.2 because it seems rather serious to me if you
> can't start jackrabbit when you don't have an internet connection, or am I
> the only one with this issue?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
