commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simone Tripodi (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DIGESTER-127) Allow DigesterLoader to accept an instance of a preconfigured Digester
Date Sun, 26 Jun 2011 17:35:47 GMT

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

Simone Tripodi resolved DIGESTER-127.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0
         Assignee: Simone Tripodi

That is possible in the Digester3 universal [DigesterLoader|https://svn.apache.org/repos/asf/commons/proper/digester/trunk/src/main/java/org/apache/commons/digester3/binder/DigesterLoader.java]
Thanks for reporting!

> Allow DigesterLoader to accept an instance of a preconfigured Digester
> ----------------------------------------------------------------------
>
>                 Key: DIGESTER-127
>                 URL: https://issues.apache.org/jira/browse/DIGESTER-127
>             Project: Commons Digester
>          Issue Type: Improvement
>    Affects Versions: 1.8
>            Reporter: Guillaume Jeudy
>            Assignee: Simone Tripodi
>            Priority: Minor
>             Fix For: 3.0
>
>
> The problem lies in the usage of a Digester with an XSD schema combined with loading
rules from an XML file with DigesterLoader.
> Digester.setSchema() is mentioned as unreliable in the javadoc, for this reason it is
preferable to create a new Digester(SAXParser) and call SAXParser.setProperty("schemalocation_proprietary_property_name",
mySchemaLocUrl);
> Unfortunately we cannot use this combination with DigesterLoader. Change DigesterLoader
to support this scenario..

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

        

Mime
View raw message