[
https://issues.apache.org/jira/browse/DAFFODIL-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Lawrence resolved DAFFODIL-3035.
--------------------------------------
Resolution: Fixed
Fixed in commit aee5c0c9123a5e937c0bdd15ac0c8614ecba52c5
> No way to create a Validator using a InputStream as a source
> ------------------------------------------------------------
>
> Key: DAFFODIL-3035
> URL: https://issues.apache.org/jira/browse/DAFFODIL-3035
> Project: Daffodil
> Issue Type: Bug
> Components: API
> Reporter: Steve Lawrence
> Priority: Major
> Fix For: 4.0.0
>
>
> The new Validator API configures validators by providing them a Java
> Properties instance, which is just a bunch of key/value pairs. There is no
> longer a way to directly create a validator using some other mechanism. The
> idea that key/value pairs should be sufficient may not be correct.
> Currently, the smooks library gets an InputStream to a schematron file,
> manually creates a custom schematron validator using that stream, and
> provides that to Daffodil. Smooks supports getting the schematron InputStream
> from a number of places, some of which might not be able to be represented as
> a string in a key/value Properties. For example, if has a custom
> "classpath:/..." uri schema that gets a stream from a classpath.
> We should figure out if there's a way we can support this. Properties only
> supports string key/values so we might need an alternative approach. Or
> possibly we just need a way to allow API users to manually create validators
> with something other than a Properties, and provide that Validator to
> Daffodil isntead of using withValidation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
