Hi
I dont think Spring 3.0 should be the default in Camel 2.2.
There are still to many other frameworks that are dependent on 2.5. It
just makes to much trouble for end users if they have to mess with
maven files to downgrade to Spring 2.5. Without noticing this you end
up with both 2.5 and 3.0
Hi,
I would also prefer if camel could stay on spring 2.5.x for a while.
It would be great though if it was already compatible to 3.0 so people
who want to switch can do this.
Greetings
Christian
Claus Ibsen schrieb:
Hi
I dont think Spring 3.0 should be the default in Camel 2.2.
There
Hi Claus,
If we don't make Spring 3.0 to be default for Camel 2.2, we will face a
problem that camel-spring-javaconfig can be built by default, as I
already upgraded the camel-spring-javaconfig to use Spring 3.0.0.
If we are OK for leave the camel-spring-javaconfig along, I'd like to
switch
On Mon, Dec 28, 2009 at 10:14 AM, Willem Jiang willem.ji...@gmail.com wrote:
Hi Claus,
If we don't make Spring 3.0 to be default for Camel 2.2, we will face a
problem that camel-spring-javaconfig can be built by default, as I already
upgraded the camel-spring-javaconfig to use Spring 3.0.0.
Yeah, we can do that by excluding the spring jars from camel-spring
which camel-spring-javaconfig depends on.
I will commit a quick fix shortly.
Willem
Claus Ibsen wrote:
On Mon, Dec 28, 2009 at 10:14 AM, Willem Jiang willem.ji...@gmail.com wrote:
Hi Claus,
If we don't make Spring 3.0 to
+1 on staying at Spring 2.5 for now.
Hadrian
On Dec 28, 2009, at 3:55 AM, Claus Ibsen wrote:
Hi
I dont think Spring 3.0 should be the default in Camel 2.2.
There are still to many other frameworks that are dependent on 2.5. It
just makes to much trouble for end users if they have to mess
On Wed, Dec 23, 2009 at 10:58 AM, Gert Vanthienen
gert.vanthie...@gmail.com wrote:
L.S.,
Do we need to maintain support for spring 2.5 java config in Camel
trunk? Wouldn't it make more sense to migrate trunk to Spring 3.0
entirely and stick to 2.5 for one or more branches? I agree we should
Good start.
Dejan created a ticket in AMQ to get it working with Spring 3.0.
And I think camel-jms depends on some API in 2.5 that was @deprecated.
So we should take a 2nd look and mark it public as @deprecated as well
in Camel 2.2.
On Tue, Dec 22, 2009 at 3:36 PM, Willem Jiang
I propose to create different tickets : one for camel, cxf, servicemix
and karaf in order to synchronise migration to spring 3.
What do you think ?
Regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*
blog : http://cmoulliard.blogspot.com
On Wed, Dec 23, 2009 at 9:47 AM, Charles Moulliard cmoulli...@gmail.com wrote:
I propose to create different tickets : one for camel, cxf, servicemix
and karaf in order to synchronise migration to spring 3.
What do you think ?
I think there is a Spring 3.0 ticket already for Camel, but could
yep.
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard
Apache Camel Group :
Just a quick updated, I managed to get ride of most failed tests in
camel-spring and camel-jms by some simple fix.
The issue for camel-spring is caused by CamelEndpointFactory, and the
issue of camel-jms is the default JMS listenContainer doesn't seem to
autostart by default anymore.
Now
L.S.,
Do we need to maintain support for spring 2.5 java config in Camel
trunk? Wouldn't it make more sense to migrate trunk to Spring 3.0
entirely and stick to 2.5 for one or more branches? I agree we should
try to make sure that Camel trunk works with 2.5 as much as possible,
but I don't
I just search the camel JIRA, and didn't find any JIRA for Spring 3.0.0.
Charles, I think you can create a new one for it :)
Willem
Charles Moulliard wrote:
yep.
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*
blog :
I think there is few people using the spring 2.5 java config,
and Spring Source doesn't maintain the Spring Java config any more
(last Spring java config milestone release is about one years ago).
So it should be OK to upgrade camel-spring-configure to use Spring 3.0.0.
Currently , camel trunk
Willem,
camel-bindy uses spring java config for its unit tests
Regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin :
Maybe we need to change it, so it can run with Spring 2.5.x and Spring
3.x at the same time.
Willem
Charles Moulliard wrote:
Willem,
camel-bindy uses spring java config for its unit tests
Regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
Oh , you are using spring-test annotation in camel-bindy, it is not the
same thing with the camel-spring-config.
The camel-bindy tests will not be effected.
Willem
Willem Jiang wrote:
Maybe we need to change it, so it can run with Spring 2.5.x and Spring
3.x at the same time.
Willem
Hi,
I just committed a spring-3.0 profile in trunk/parent/pom.xml.
You can build the camel with spring 3.0.0 by using -Pspring-3.0
I just run some test in camel-core , camel-spring and camel-jms.
There about 4~5 tests are failed in camel-spring, and lots of tests
failed in camel-jms.
For the
19 matches
Mail list logo
