-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: isDirty problem with simple transaction select
PostPosted: Tue Sep 08, 2009 8:34 pm 
Beginner
Beginner

Joined: Fri Sep 12, 2008 10:55 am
Posts: 33
Running this basic JUnit
Code:
@TransactionConfiguration( transactionManager = "transactionManager", defaultRollback = false )
@Transactional( propagation = Propagation.REQUIRED )
public class DesignationTest extends AbstractTest
{
    @Resource
    private GenericDAO<Designation, Integer> designationDAO;

    @Test
    public void getDesignations()
    {
        List<Designation> list = designationDAO.findAll( 1, 5 );

        for( Designation desig : list )
        {
            System.out.println( "Id: "
                + desig.getId()
                + " : Code: "
                + desig.getDesignationCode()
                + " : Description :"
                + desig.getDesignationDescription()  );
        }
    }
}


I end up with logs showing
...SELECT ... FROM T_DESIG....

then immediately after the System.out logging , I get
update T_DESIG ...

How can it be dirty when it's a basic Spring @Transaction managed query? This has got to be something simple?

(It does this in my server as well, so it's not JUnit)


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.