Return-Path: 
 <camel-dev-return-6220-apmail-activemq-camel-dev-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-camel-dev-archive@locus.apache.org
Received: (qmail 69944 invoked from network); 8 Oct 2008 03:30:21 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 8 Oct 2008 03:30:21 -0000
Received: (qmail 65634 invoked by uid 500); 8 Oct 2008 03:30:20 -0000
Delivered-To: apmail-activemq-camel-dev-archive@activemq.apache.org
Received: (qmail 65613 invoked by uid 500); 8 Oct 2008 03:30:20 -0000
Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:camel-dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:camel-dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:camel-dev@activemq.apache.org>
List-Id: <camel-dev.activemq.apache.org>
Reply-To: camel-dev@activemq.apache.org
Delivered-To: mailing list camel-dev@activemq.apache.org
Received: (qmail 65602 invoked by uid 99); 8 Oct 2008 03:30:20 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Oct 2008 20:30:20 -0700
X-ASF-Spam-Status: No, hits=-1999.7 required=10.0
	tests=ALL_TRUSTED,DNS_FROM_SECURITYSAGE,WHOIS_MYPRIVREG
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Oct 2008 03:29:16 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 9703A234C1E4
	for <camel-dev@activemq.apache.org>; Tue,  7 Oct 2008 20:29:52 -0700 (PDT)
Message-ID: <1970328422.1223436592604.JavaMail.jira@brutus>
Date: Tue, 7 Oct 2008 20:29:52 -0700 (PDT)
From: "Hadrian Zbarcea (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Updated: (CAMEL-390) if folks overload xmlns to use camel,
 then define beans with <bean ...> Camel should generate an error with a
 useful error message
In-Reply-To: <35684969.1205855732629.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/activemq/browse/CAMEL-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hadrian Zbarcea updated CAMEL-390:
----------------------------------

         Assignee: Hadrian Zbarcea
    Fix Version/s: 2.0.0
                       (was: 1.5.0)

I am not sure this is a valid issue yet.  I suspect the xml is not correct but I only have briefly looked into it.  If I understand correctly this is related to the use of refs.

It's ok for the xml doc to have one default namespace and than one element (<camelContext>) to redefine the default namespace to be something else.  However, since we are dealing with qnames, the camelContext element should define a different namespace mapping (and a prefix) for the default namespace of the document (the spring namespace) and use that to qualify the element it refs, so that resolution can happen.

But then again, I may have misunderstood the issue completely.  I'll look into it soon though.

> if folks overload xmlns to use camel, then define beans with <bean ...> Camel should generate an error with a useful error message
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-390
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-390
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: James Strachan
>            Assignee: Hadrian Zbarcea
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> See this thread... http://www.nabble.com/BeanFactoryAware-%28Spring%29-tp16122107s22882p16124218.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.