Return-Path: 
 <issues-return-13245-apmail-camel-issues-archive=camel.apache.org@camel.apache.org>
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 8881E10EE5
	for <apmail-camel-issues-archive@minotaur.apache.org>;
 Sun,  6 Oct 2013 21:31:45 +0000 (UTC)
Received: (qmail 16374 invoked by uid 500); 6 Oct 2013 21:31:45 -0000
Delivered-To: apmail-camel-issues-archive@camel.apache.org
Received: (qmail 16301 invoked by uid 500); 6 Oct 2013 21:31:44 -0000
Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@camel.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@camel.apache.org>
List-Post: <mailto:issues@camel.apache.org>
List-Id: <issues.camel.apache.org>
Reply-To: dev@camel.apache.org
Delivered-To: mailing list issues@camel.apache.org
Received: (qmail 16135 invoked by uid 99); 6 Oct 2013 21:31:43 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Oct 2013 21:31:43 +0000
Date: Sun, 6 Oct 2013 21:31:42 +0000 (UTC)
From: "Eugene Tarasov (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12670840.1380232291974.23438.1381095102938@arcas>
In-Reply-To: <JIRA.12670840.1380232291974@arcas>
References: <JIRA.12670840.1380232291974@arcas>
Subject: [jira] [Reopened] (CAMEL-6790) Resuming a bundle that uses
 blueprint+camel fails if it was suspended externally
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-6790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eugene Tarasov reopened CAMEL-6790:
-----------------------------------


> Resuming a bundle that uses blueprint+camel fails if it was suspended externally
> --------------------------------------------------------------------------------
>
>                 Key: CAMEL-6790
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6790
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-blueprint
>    Affects Versions: 2.12.1
>            Reporter: Eugene Tarasov
>            Assignee: Claus Ibsen
>             Fix For: 2.11.3, 2.12.2, 2.13.0
>
>
> There is a problem in this scenario:
> # Karaf is running.
> # Start some bundle that uses blueprint+camel. For convenience will call it <testbundle>.
> # Cause this bundle to be suspended by container, by refreshing a bundle that provides some namespace used by <testbundle> bundle. For example, by refreshing camel-cxf (assuming that <testbundle> uses also blueprint/cxf namespace). In logs one can see something like this:
> bq. Bundle <testbundle> is waiting for namespace handlers [http://camel.apache.org/schema/blueprint/cxf]
> In this case after the missing namespace becomes available again the bundle will fail to resume with exception like:
> bq. Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'camelContext'.
> The problem is in CamelNamespaceHandler class which is a part of camel-blueprint. When it parses incoming dom it changes namespace of all elements from http://camel.apache.org/schema/blueprint to http://camel.apache.org/schema/spring. So when a bundle that uses blueprint+camel needs to validate its blueprint context again (like if it was waiting for some namespace) the new validation will fail.



--
This message was sent by Atlassian JIRA
(v6.1#6144)