Hi Federico,
I looked into it a bit more and realized the issue was due to autowiring the
Camel context through the constructor of the test class.
https://gist.github.com/0x6A75626172/c7aa6c1c925087a11fa0f836dd6add76
When I autowire the fields directly like your reproducer it also works for me.
T
Hi Jubar,
I think I reproduced a similar scenario, and the test is successful,
https://gist.github.com/Croway/24ba7620d52ed528aa13e13c70678e25 can you
share a reproducer? in particular, without the DirtiesContext, the 2nd test
fails on the first assertion, due to Camel Context already started,
oth
I got it. If our user use camel-test-spring, he will likely do it by
annotating it with CamelSpringJUnit4ClassRunner or by extending
CamelSpringTestSupport.
For the first case, he needs spring-test, but not for the second one.
If we didn't had to use Spring 3.1.x for this (say Spring 3.0.x would a
I don't have an issue with it since I found the work-around.
It is more that it took me a couple of hours to figure it out (probably
some of it due to inexperience since I first thought I had a problem with
my application-context).
And is Willem says it is an intermediate problem that will go away
If the user doesn't use the CamelSpringUnit4ClassRunner from the
camel-test-spring, he doesn't need the spring-test:3.1.x.
But if he needs it, he should consider to update the spring dependency
version.
When we upgrade the spring version to 3.1.x, these issues will go away.
On Wed Apr 25 06:42
Sorry, forget my last comment...
I think we should let it is as it is.
I created a sample application which depends on camel-sql and
camel-test-spring. The dependency tree looks like below (dependency to
org.springframework:spring-test:3.1.1.RELEASE):
[INFO] --- maven-dependency-plugin:2.1:tree (
At present, the dependency tree looks like below (which is wrong):
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @
camel-test-spring ---
[INFO] org.apache.camel:camel-test-spring:bundle:2.10-SNAPSHOT
[INFO] +- org.apache.camel:camel-test:jar:2.10-SNAPSHOT:compile
[INFO] | +- org.apach
On Thu, Apr 19, 2012 at 3:20 PM, Willem Jiang wrote:
> On Thu Apr 19 16:40:05 2012, Magnus Palmér wrote:
>>
>> It works when adding spring-context dependency 3.1.1 to my pom.
>
>
> I just checked the code of camel-test-spring, if you are using the
> CamelSpringJUnit4ClassRunner, you need to use th
On Thu Apr 19 16:40:05 2012, Magnus Palmér wrote:
It works when adding spring-context dependency 3.1.1 to my pom.
I just checked the code of camel-test-spring, if you are using the
CamelSpringJUnit4ClassRunner, you need to use the Spring 3.1.1.
As the CamelSpringTestContextLoader doesn't supp
It works when adding spring-context dependency 3.1.1 to my pom.
What you are saying works for camel-test-spring since the spring
dependencies are managed explicitly, maybe that is good practice?
I am not that experienced with spring yet.
Maybe it should say something about it in the wiki for spri
There are compiling issue of camel-test-spring with spring 3.0.x, but
it should work by just applying the jar into the class path.
You can override the spring version in your pom this time.
On Thu Apr 19 05:23:07 2012, Magnus Palmér wrote:
In the camel-parent pom:
3.0.7.RELEASE
And in camel-t
In the camel-parent pom:
3.0.7.RELEASE
And in camel-test-spring pom:
3.1.1.RELEASE
Den 18 april 2012 23:12 skrev Magnus Palmér :
> I ran into some trouble today when I changed my JUnit test to use
> @RunWith(CamelSpringJUnit4ClassRunner.class) from camel-spring-test
>
> It turned out that a tran
12 matches
Mail list logo
