Hi I would like to know which camel version is used in Fuse esb (jboss-fuse-6.0.0.redhat-024),
according to the migration guide it's 2.10.0 .
how can I update it to use 2.10.5 ?
JBoss fuse is using customer version of Camel which is based on the Camel 2.10.x branch.
As there are lots other projects which may relates to this Camel version, I don't suggest you to change the version yourself.
Related
I wonder if it is possible to integrate an old version of a Camel component, with an application of a newer Apache Camel version. In my case I want to integrate to Hbase server version 1.2, that is supported only with HBase client 1.2. Therefore even though I want to use a 3.1 Camel version, I want to use the 3.0.1 version of Camel-HBase component. Is it a fine thing to do?
Or is there any place that I can see the versions of the libraries Apache Camel supports?
You can check the Camel dependencies POM to find the versions of dependencies that are imported by the different components.
See the dependencies POM of Camel 3.10.x. You will find <hbase-version>2.3.1</hbase-version> in it.
Another source is Maven Central where you can see the dependency versions of a specific Camel component version.
See Camel-HBase 3.1.0 that references Hbase-client 1.2.6.
However, normally one cannot choose the Camel version to match a specific component dependency version. In general it is the other way round. You want or have to work with an already existing version or you want to use a current version to get the best of the framework.
If you build a new application with Camel 3.10.x, you get the hbase-client in version 2.3.1.
If newer Hbase client versions are not compatible with Hbase 1.2 it becomes difficult.
you get lots of problems when you mix and match Camel component versions
even if you can build your application with an older Camel version, you could never upgrade
The only solution I see would be to isolate the Hbase integration in its own (freezed) application with an older Camel version that matches your desired Hbase-client version.
I am using camel-salesforce component in jboss-fuse-karaf-6.3.0.redhat-187. Camel version 2.18.x provide replay with push-topic. If the client subscription got lost we can replay the old notification.
As per Red hat component details page , JBoss Fuse 6.3 support camel version 2.17.0.
https://access.redhat.com/articles/348423
Is there any way we can use camel 2.18.x version with jboss-fuse-karaf-6.3.0.redhat-187, so we use salesforce replay.
Will highlty appreciate if someone could provide any link , document or any red hat jira issue.
We already tried different stuff
1.) Try to merge 2.18 replay classes with 2.17 , there is lot of changes in 30-40 classes so tough doable.
2.) Try to build with 2.18 classes with 2.17 jars .Still not worked with karaf
3.) Fuse 6.3 not support camel 2.18.x so directly using 2.18 not making sense.
Kindly let me know if need any further information.
Thank you so much in advance.
No you should use the version that is shipped with JBoss Fuse, that is the certified version. Use Red Hat customer portal to get help/support with your fuse product. If there is a bug/feature in camel-salesforce you are looking for in JBoss Fuse 6.3 that is only available in later Camel release, then the Red Hat team can help you by looking into whether that can be backported and provided to you or what else you can do.
I have been working with Jboss Fuse 6.1.0.redhat-379 for about a month with great results and higher productivity in EIP. Thank you very much to the community for building such a great product.
Now I am getting ready to deploy my bundles in a dev enviroment with several camel routes and even multiple camel contexts in a single bundle and I'm noticing a weird behavior regarding camel contexts JMX display. The bundle with the multiple camel contexts is only showing the first context, others contexts work fine but they are missing in camel JMX display in hawtio.
After research about this behavior I encountered with this JIRA issue https://issues.apache.org/jira/browse/CAMEL-7545 opened by Claus, describing exactly this problem and manifesting that there are Fix Versions (2.12.4, 2.13.2, 2.14.0)
AFAIK my Jboss Fuse version is distributed with camel 2.12.0.redhat-610379 version and there is a mayor 2.14.0.redhat-620031 version that supposedly will fix this issue and it will be bring many other features like json path and sql generated keys.
Is there a way to upgrade versions of camel features in Jboss Fuse?
UPDATE
There is a similar question for this topic (Updating camel version in fuse esb) accepted answer discourages trying to update the version, however, I think it should be better to permit version upgrades if they fix issues
Not a 100% on this but the rollup patches might include the 2.12 fixed versions. Install the latest patch and see if that fixes the issue.
I have been trying my head around the camel NMR component and wanted to practice some of use cases on servicemix platform. But to my surprise, I could not find the nmr feature in servicemix 5.3 version which I have.
Is support for NMR in servicemix withdrawn? Please help me understand this.
Yes JBI support in ServiceMix 5.x is dropped. JBI is dead, do not use that.
The NMR component was part of JBI and hence dropped.
Just use pure Camel in ServiceMix.
http://servicemix.apache.org/docs/4.4.x/jbi/components/servicemix-camel.html
http://gnodet.blogspot.se/2010/12/thoughts-about-servicemix.html
NMR is not available but we can use direct-vm component which is working same as NMR.
i want to install the apache camel tools for eclipse: http://tools.jboss.org/features/apachecamel.html
But how to install/ where to find camel tools? I tried to install JBoss Tools from eclipse marketplace but didn't find camel on selection screen. (don't want all tools)
I also tried the update site mentioned here http://tools.jboss.org/blog/2014-04-14-JBTIS-4.html but the only "camel" thing is "JBoss Fuse Camel Editor Feature" is this it?
Besides the visualizing of routes i want to see jmx stuff that is exposed by my camel app.
The blog entry from Paul Leacu provides the correct information. There are currently 3 features which are named like "JBoss Fuse ...".
The Camel Editor feature provides the editor for designing your Camel Routes and to launch them on your local machine.
Then there is the Fuse Server Adapter feature which provides some server adapters for starting / stopping / installing Apache ServiceMix, Apache Karaf and JBoss Fuse servers.
Finally there is the Fuse Runtime feature which provides the JMX stuff you are looking for and the Fabric related functionality.
I made a short install guide on how to install JBoss Fuse Tooling without JBDS and/or the integration stack. You can find the guide here.