No, the changes will be written to the database - have you inspect the hibernate logging? (Maybe you have to enable it in your persistence.xml)
But the changes won't be visible to other sessions until they are committed - normally automatically at end of the event (after leaving your method).
So you have either to bypass the transaction handling and do it by yourself (using SEAM's user transactions) or use another approach to signal the progress to other sessions, e. g. SEAM events.
Ich think the latter would be a very better method because it avoids polling on database tables which may kill your database performance in a multi user environment.
Thanks for your response.
I think i will handle the transaction handling by myself. I also have found
this great thread: