Tank you for the answers!
I can now see that I mixed up names and things and frameworks. Fuse is based
on Karaf; when you start (RedHat) Fuse you meet Karaf console.
And about testing Camel osgi-blueprint routes: Check Camel in Action: in
the osgi example of the book, there is not even
On Wed, Jul 23, 2014 at 9:21 AM, user3152723
unto.valko...@fifthelement.fi wrote:
Tank you for the answers!
I can now see that I mixed up names and things and frameworks. Fuse is based
on Karaf; when you start (RedHat) Fuse you meet Karaf console.
And about testing Camel osgi-blueprint
Hi
Apache Camel is a library that is intended to be used in any kind of
environment. Whether you run Camel in OSGi / JEE / Standalone / micro
containers / or whatever.
All the Camel components / DSLs etc is designed to work the same.
So from Camel point of view you do not miss out running
Ups meant to add OSGi in there as well
Well IMHO a big part of f the learning curve is IMHO and the fact that
Karaf is a new kind of application server, that most people have not
used before.
Should be
Well IMHO a big part of f the learning curve is OSGi and the fact that
Karaf is a new kind
Hi,
thanks for your reply! Camel is just great framework and your book is a must
resource for Camel user (says ex Mule user).
Still I'd like to insist to hear your opinion: when do we not need to use
blueprint osgi? It seems to me that if you use current version of Fuse, you
can't but use
On Wed, Jul 23, 2014 at 10:22 AM, user3152723
unto.valko...@fifthelement.fi wrote:
Hi,
thanks for your reply! Camel is just great framework and your book is a
must resource for Camel user (says ex Mule user).
Still I'd like to insist to hear your opinion: when do we not need to use
It is recommended to use blueprint with Camel if you run your routes on osgi.
But what would you miss out if your choose to run Camel routes in / imbedded
in Spring (SpringBoot) in stead of Karaf? You anyway get the ease of testing
with Spring.
Using Fuse : Camel, Activemq, and starting with
That is what official Red Hat Fuse ESB Enterprise documentations says:
When trying to decide between the blueprint and Spring dependency injection
frameworks, bear in mind that blueprint offers one major advantage over
Spring: when new dependencies are introduced in blueprint through XML schema
I think it is also a question of modularity/concern.
The major subject of Camel is to make routes between services (EIPs).
So everytime you deploy a new service (and so modify your routes) you'll
have to stop and restart them.
Now, if you have mutliple routes on the same Vm and use Spring, a
For testing, you have some frameworks with OSGI too:
* You can use Spring for unit testing (it will replace blueprint as test
context)
* You can use pax-exam (maybe with karaf-pax-exam-container) for
integration testing (all your stack, as you would do with spring/tomcat)
2014-07-22 13:59
Fabric only supports Karaf right now, but it's supposed to add support for
more servers over time (I think Tomcat or Jetty was one of them).
On 22 July 2014 10:47, Charlie Mordant cmorda...@gmail.com wrote:
For testing, you have some frameworks with OSGI too:
* You can use Spring for unit
11 matches
Mail list logo
