You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Sami Nurminen (JIRA)" <ji...@apache.org> on 2015/08/14 18:48:46 UTC

[jira] [Commented] (CAMEL-5716) Validator - schema from memory/property

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

Sami Nurminen commented on CAMEL-5716:
--------------------------------------

I could try to implement this.
If schema (XSD XML string) is provided in header, then 
component will use that. 

Should these "dynamic" schemas be cached (for example in limited size LRU cache)? Caching could be configurable(yes/no, maxSize etc.).


> Validator - schema from memory/property
> ---------------------------------------
>
>                 Key: CAMEL-5716
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5716
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.10.1
>            Reporter: Petter Nordlander
>            Priority: Trivial
>              Labels: patch
>             Fix For: Future
>
>
> As far as I understand, the validator "component" in Camel can only use schemas deployed as file within the classpath (typically the deployed application - ear/war/jar whatever have you) or some file/http resource. 
> Sometimes you might want to load the schema a bit more dynamically, I.E. from some datasource or semi-generate something on the fly. My suggestion is that a schema could be supplied in a propery or a header to the validator.
> I wrote such an extension to the validator and could probably rewrite it easily as a patch to the regular validator. Do you think people want to use such a feature and that it might be good to have in Camel? Should I submit a patch?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)