[
https://issues.apache.org/jira/browse/CAMEL-9166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908163#comment-14908163
]
Jyrki Ruuskanen commented on CAMEL-9166:
----------------------------------------
Thanks man for taking a look at this. The reason I'm interested in backward
compatibility and avoiding ABI changes is the fact that we are using camel-scr
in production with Fuse 6.x. The ability to use the same bundles (using
camel-scr) across Fuse and Camel versions (Fuse 6.1 -> 6.2 -> 6.2.1 -> 6.?)
makes things simpler. I don't know how far the Camel versions will be pushed in
Fuse 6.x but I would hate to see breaking changes in Fuse 6.2.1 (Camel 2.15.3?).
In other words, in my opinion camel-scr ABI should not change within Camel 2.15
(as now happened with 2.15.3). In 2.16 it's fine, there are changes that could
make the component better.
The current starting logic is a compromise between simple/silly and
complex/correct. It doesn't actually try to start the Camel context every 5th
second but 5 seconds after the last CamelComponent has been registered which
typically only happens once. The correct way requires us to extract a complete
list of required components from the routes in the context and wait for the
list to be satisfied before starting. It's not clear to me how I can get that
list.
> Some functionality broken in Camel-8857
> ---------------------------------------
>
> Key: CAMEL-9166
> URL: https://issues.apache.org/jira/browse/CAMEL-9166
> Project: Camel
> Issue Type: Bug
> Components: camel-scr
> Affects Versions: 2.15.3, 2.16.0
> Reporter: Jyrki Ruuskanen
> Assignee: Claus Ibsen
> Fix For: 2.16.0
>
>
> Changes in Camel-8857 cause properties prefixing to not work for Camel
> context ID. See notes in
> https://github.com/apache/camel/commit/aa59cec696c46d4f9398ae91410998bd40fabbaa.
> Also, backward compatibility to 2.12.0 is removed. See note in
> https://github.com/apache/camel/commit/c1b33e990ae5da7ca1e0268e79acc728393fd3ae.
> Camel-8857 also had ABI changes that break existing bundles (requires
> rebuilding them all).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
