[ 
https://issues.apache.org/jira/browse/WODEN-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062759#comment-13062759
 ] 

Ranjana Prasad edited comment on WODEN-72 at 7/10/11 4:44 PM:
--------------------------------------------------------------

Attach first patch. Please test and let me know if you find any issue. 

      was (Author: ranjana):
    Attach a first patch. Please test and let me know if you find any issue. 
  
> OASIS-style URI Resolver
> ------------------------
>
>                 Key: WODEN-72
>                 URL: https://issues.apache.org/jira/browse/WODEN-72
>             Project: Woden
>          Issue Type: New Feature
>          Components: Parser
>            Reporter: Graham Turrell
>         Attachments: woden-patch1.txt
>
>
> The OASIS standard for URI resolvers (TR9401) has a number of feature 
> advantages over the SimpleURIResolver implemented as part of WODEN-14.
> For example:
> - Catalog files are specified in terms of a standard XMl Schema;
> - Root URIs can be defined such that all descendants of a remote root are 
> mapped to a corresponding local root;
> - Ability to wrap local URI-resolved files into jars
> - Chaining of catalogs
> An arguable disadvantage for the user is the relative complexity of creating 
> the catalog compared to the Simple URI resolver (based on java properties 
> files).
> Such an implementation exists in the xml-commons resolver.jar. To make use of 
> this, a Woden Resolver adaptor class would be defined to attach the 
> implementation into the Woden resolver framework.  The choice of resolver 
> implementation (Simple or OASIS) can be left to runtime but the choice of 
> which should be default is of course a design issue. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to