Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 883E418786 for ; Tue, 16 Feb 2016 13:02:18 +0000 (UTC) Received: (qmail 68288 invoked by uid 500); 16 Feb 2016 13:02:18 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 68246 invoked by uid 500); 16 Feb 2016 13:02:18 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 68236 invoked by uid 99); 16 Feb 2016 13:02:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Feb 2016 13:02:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 2158B2C14F4 for ; Tue, 16 Feb 2016 13:02:18 +0000 (UTC) Date: Tue, 16 Feb 2016 13:02:18 +0000 (UTC) From: "Franz Forsthofer (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Work started] (CAMEL-9572) Validator Component: Support custom resource resolver which depends on dynamic resource URI of the endpoint MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-9572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-9572 started by Franz Forsthofer. ----------------------------------------------- > Validator Component: Support custom resource resolver which depends on dynamic resource URI of the endpoint > ----------------------------------------------------------------------------------------------------------- > > Key: CAMEL-9572 > URL: https://issues.apache.org/jira/browse/CAMEL-9572 > Project: Camel > Issue Type: Improvement > Components: camel-core > Reporter: Franz Forsthofer > Assignee: Franz Forsthofer > Fix For: 2.17.0 > > Attachments: 0001-Validator-support-custom-resource-resolver-factory.patch > > > The validator endpoint allows already to specify custom resource resolvers, via the parameter resourceResolver. However, there is a use case where this functionality is not sufficient. If you have a dynamically created validator endpoint, like > > validator:${header.XSD_FILE}?resourceResolver=#resourceResolver > > where the resource URI of the XSD document is also dynamic (in the example via the header XSD_FILE) and if your resource resolver depends on the resource URI of the XSD document, then the current implementation gives you no solution for this problem. You cannot hand-over the dynamic resource URI to the custom resource resolver. > Therefore we introduce the new parameter resourceResolverFactory where you can specify a factory which implements the method > LSResourceResolver createResourceResolver(CamelContext camelContext, String rootResourceUri); > This method is called when the endpoint is created and gives you access to the endpoint resource URI (parameter rootResourceUri). > Remark: resource resolvers need to have the root resource URI in the case of relative URIs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)