jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ard Schrijvers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OCM-35) OCM DTD offline resolution
Date Wed, 27 Jun 2012 14:30:45 GMT

     [ https://issues.apache.org/jira/browse/OCM-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Ard Schrijvers updated OCM-35:

    Resolution: Invalid
        Status: Resolved  (was: Patch Available)

there is no ocm dtd any more afaics
> OCM DTD offline resolution
> --------------------------
>                 Key: OCM-35
>                 URL: https://issues.apache.org/jira/browse/OCM-35
>             Project: Jackrabbit OCM
>          Issue Type: Improvement
>            Reporter: Craig Schaefer
>            Priority: Minor
>         Attachments: OCM-35.patch
> OCM xml descriptor files will sometimes specify the DTD for OCM
> e.g. 
> <!DOCTYPE jackrabbit-ocm PUBLIC "-//The Apache Software Foundation//DTD Jackrabbit
OCM 1.5//EN" 
>                          "http://jackrabbit.apache.org/dtd/jackrabbit-ocm-1.5.dtd">

> When this happens the XML parser will attempt to resolve the DTD over an internet connection.
 This is 1) generally inefficient and 2) assumes the backend with JCR-OCM can always reach
the internet.  Point 2 in particular is never guaranteed and so to borrow the local resolution
concept from other great libraries like spring it would be better to locally provide and resolve
the DTD for OCM.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message