Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <1874549346.1254500580813.JavaMail.jira@brutus>
Date: Fri, 2 Oct 2009 09:23:00 -0700 (PDT)
From: "Guillaume Nodet (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-2021) Schema versioning for camel-spring
 schema
In-Reply-To: <1582094431.1253200872236.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Guillaume Nodet commented on CAMEL-2021:
----------------------------------------

Yeah, we need to ship two different schemas.
The unversioned one (which is currently provided) would allow full backward compatibility and also allow users to not care about the camel's version they use.
The versioned one would tie to route definition to a given camel version, but would allow deploying different camel versions in the same osgi container.

> Schema versioning for camel-spring schema
> -----------------------------------------
>
>                 Key: CAMEL-2021
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2021
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-spring
>    Affects Versions: 2.0.0
>            Reporter: Guillaume Nodet
>            Assignee: Willem Jiang
>             Fix For: 2.1.0
>
>
> Given the camel-spring schema is not versioned, we have no way in OSGi to install two different versions of camel and for a given bundle, choose the version of camel for the routes.

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