Why don't you want them to rollback? If you're going to manually check
your database to see if it worked - that's not a very good way to
test.
Yes, you can use setComplete() to force a commit w/o a rollback, but
you should automate the testing and use jdbcTemplate.queryForObject()
- or something l
mraible wrote:
>
> There's a jdbcTemplate available for you to query the database with.
> Matt
>
Thx Matt,
Can I do it without go down on jdbcTemplate using only GenericManagers or
its extensions ?
Here a trace of my code:
public class AnamnesiTest extends BaseDaoTestCase{
public void tes
There's a jdbcTemplate available for you to query the database with.
Matt
On Nov 14, 2007 4:15 AM, Campa <[EMAIL PROTECTED]> wrote:
>
> Hi guys,
>
> I'd like to have unit test that commit something to the DB, as default
> seems they never commit.
> I'm right ?
>
> I see the message:
>
> [webCps]
Hi guys,
I'd like to have unit test that commit something to the DB, as default
seems they never commit.
I'm right ?
I see the message:
[webCps] INFO [main] AnamnesiTest.startNewTransaction(323) | Began
transaction (1): transaction manager
[EMAIL PROTECTED]; default rollback
= true
How I can
