Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Mon, 22 Aug 2011 14:34:29 +0000 (UTC)
From: "David J. M. Karlsen (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <646347171.1246.1314023669568.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <138121954.56740.1313945487404.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CAMEL-4361) Improve validator to accept several
 schemas
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

David J. M. Karlsen commented on CAMEL-4361:
--------------------------------------------

So if "my" component will depend on: http://static.springsource.org/spring-ws/sites/1.5/spring-xml/apidocs/org/springframework/xml/xsd/commons/CommonsXsdSchema.html and org.apache.ws.commons.schema.XmlSchemaCollection then i guess I should stick it into camel-spring?

> Improve validator to accept several schemas
> -------------------------------------------
>
>                 Key: CAMEL-4361
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4361
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-spring
>    Affects Versions: 2.8.0
>            Reporter: David J. M. Karlsen
>
> The current implementation only allows for one given xsd schema.
> I have some messages which have two namespaces. The outer schema declares some elements with lax processing.
> By providing a http://static.springsource.org/spring-ws/sites/1.5/spring-xml/apidocs/org/springframework/xml/xsd/XsdSchemaCollection.html which references both schemas I would be able to validate the whole message - and not just the outermost one.
> Either the existing implementation will have to be altered to allow for several paths, or it can be extended to reference a schemacollection.

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