[ https://issues.apache.org/jira/browse/OCM-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Schaefer updated OCM-35: ------------------------------ Attachment: OCM-35.patch OCM-35.patch > 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. - You can reply to this email to add a comment to the issue online.