On Wed, Mar 24, 2010 at 6:52 PM, Kevin Jackson <foamd...@gmail.com> wrote: > Hi, > > To clear this whole thing up - I can now report that everything is > working as expected, the problem was (and still is) with Spring's > transactional test support, not rolling back the data that my > processing is adding to the database. This meant that I was checking > against an old value in the db and getting a test failure - the > correct value was also in the db. > > So the problem has moved from Camel to Spring @Transactional, which is > quite interesting as it works for other tests, just not this > particular one. >
There used to be a issue in Camel with using CGLib proxied Spring beans, but I recall that was fixed in 2.2 as well. And that issue was only when you used Camel @annotations which causes them to not work as expected. Spring @Transactional is to my knowledge working. Maybe the Spring log can help. It logs something about bean XXX not eligible for bean post processing, which is the process Spring does when applying @ annotations and whatnot. > Thanks for the help and I will not post unless I have exhausted the > other possibilities. > Kev > Maybe I went a bit overboard. But the point is that people should refrain from posting 2 min after they hit an issue. And instead spend some time looking into the issue. And trying out with latests releases is also preferred as it may very well be fixed. -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
