jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Schaefer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OCM-35) OCM DTD offline resolution
Date Fri, 19 Jun 2009 15:20:07 GMT

    [ https://issues.apache.org/jira/browse/OCM-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721813#action_12721813

Craig Schaefer commented on OCM-35:

General approach is simpliar to that of Spring.  The DTD is included in the ocm jar under
META-INF.  The user of the descriptor reading code can still choose to resolve the DTD to
their own variant as before or at least to the default offering.

However now at least when the DTD clause is included in an OCM mapping descriptor then at
least by default DTD resolution will occur locally and not attempt to hit the network which
may not always be there.

> 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.

View raw message