Hmmm,...never mind. Converted to Junit4 and the SpringJUnit4ClassRunner which made the problem dissappear (still have no clue why it didn't work with spring-mock-2.0.8+spring-3.0.3).
Type: Posts; User: polesen; Keyword(s):
Hmmm,...never mind. Converted to Junit4 and the SpringJUnit4ClassRunner which made the problem dissappear (still have no clue why it didn't work with spring-mock-2.0.8+spring-3.0.3).
Ooh yeah, one important thing I forgot to mention:
This fails from spring-mock 2.0.8 tests only!!! When the applicationContext is bootstrapped through a testcase that inherits for instance...
Hi,
Is there anything special I need to do in the config, to make springs @Qualifier work with 3.0.3? I had this perfectly working with 2.5, but after an upgrade, it does not. No code changes...
Two things:
1. Did you get anywhere with this. I need the same, and am considering building it myself. Maybe simply an aspect applied via an annotation.
2. Don't assume that a batch_mutate is...
Hi Jörg,
Nope. They do not.
I've been digging a little. I think the problem is due to me having some xfire config where I'm using JSR-181 annotations. I then define a xfire postprocessing...
I think I've done everything as the docs says and still, it fails on me.
I have a bean defined in scope request like this:
<bean id="currentPrincipal"...
Hi,
I have a situation where I need to access two different databases through two different data sources. I would like to use declarative transactions through the @Transactional annotation. But,...