Hi,
yes this setup looks good to me,
just one note, don't know if you're already doing it, for the camel part
make sure it is all blueprint / JavaDSL for the Camel route :)
Ok, now since I have this picture, the big headaches are regarding the
apples and oranges bundles,
cause those need spring.
Achim and Tim, thank you for your help!
Achim Nierbeck wrote
yes this setup looks good to me,
just one note, don't know if you're already doing it, for the camel part
make sure it is all blueprint / JavaDSL for the Camel route :)
Yes, I always use JavaDSL to define Camel routes. In Spring
Hi,
good that it works with Spring 3 :), at least this can be the basis of some
Discussion and or development and might take some pressure of this part of
the project ;)
regarding the camel part, for simplification (and again to reduce the
spring-dependencies) I'd switch that part over to
Achim Nierbeck wrote
4) Re-Package the spring-dm bundles or alter the Manifest for the version
Range. This can either be achieved with 1) using the maven-shade-plugin
and
an adapted Manifest file that widens the import range to [2.5.6, 4.1) or
[2.5.6, 5). Another possibility, alter the
Hi,
no, this wouldn't require a compile time dependency.
You just need an extra module in your project setup.
a/ a module containing the re-packaged Spring-DM including as feature
b/ a module containing either one or more fragment bundles to alter the
Version-Range.
With a) you'd need to add an
I am not sure if I am helping here but the spring-dm feature depends on
spring [2.5.6,4) as seen below
root features:info spring-dm
Description of spring-dm 1.2.1 feature
Feature has no configuration
Feature has no configuration
Why do I need Spring? Do you mean for the DI wiring, or in general? ;) Lots
of our application code/services have been developed with Spring, Spring has
been used not only for DI, but for many other things, of course. I, of
course, understand that the traditional Spring framework (not Spring-DM)
Hi,
From your description I still can't see your issue. Maybe you should tell
us more about what you are up to.
Are you trying to run multiple spring versions with spring-dm?
How is your setup?
Do you only manually install the spring feature. Do you reference the
desired spring feature in your
Hi,
I'm gonna try to give you a quick response and will get back to this mail
later with a bit more time.
First of all I'm not suggesting to drop spring, you've been referring to
camel at one point that's where I've got the impression that you might only
need blueprint.
But it might help already
Achim, thanks so much for taking the time to look into this and help me out.
My original architectural approach (that has worked for me before) has been
the following. I have a set of well-defined bundles, where one bundle
consolidates some common (reusable, to be shared with other bundles)
the
desired spring feature in your feature.xml?
Regards, Achim
I am not using multiple versions of Spring. Originally I was trying to use
the out-of-the-box spring 4.0.2 and spring-dm versions provided by the
container. In my features.xml I have tried including the following:
feature
archive that an admin would drop into
the container and forget about it. So, I would really like to understand
which core Karaf features must be available and activated (and which must be
disabled, if any) to ensure that my [fairly simple] Camel/Spring
4.0.2/Spring-DM application deploys as a KAR
Hi,
Before running this with a KAR I'd start with using a feature only first.
For example install the needed features with the she'll per command. After
that, install your feature also via command. If this succeeds try with
adding dependencies to your feature and install your feature only via
Actually, spoke too soon. The bundles deploy without errors, but no Spring
context is initialized in any of the bundles at all! Crying for help...
--
View this message in context:
http://karaf.922171.n3.nabble.com/Spring-4-0-2-and-spring-dm-tp4033093p4033096.html
Sent from the Karaf - User
4.0.2.RELEASE_1) and spring-dm (v.
1.2.1) features are installed/activated. I even tried explicitly
uninstalling Spring 3.2.4.RELEASE. However, I am always getting the
following exceptions when deploying the KAR file:
Offending resource: URL
[bundle://126.0:0/META-INF/spring/my-bundleX-context.xml
15 matches
Mail list logo
