hi thx for your intput. it's exactly as you expected it, the bean later calls other beans, within the same transaction. at this point, the async bean already startet with the work.
i think, that the EntityManger.flush() method does not help me, because the date is transfered to the DB, but not commited, and therefore not visible for the message driven POJO. at the moment my solution is to use "bean managed transaction" @TransactionManagement(TransactionManagementType.BEAN) , which is not so nice, because i need to control the whole bean no myself... best for me would be the normal JTA container managed transaction with a little "extra" rule, to sometimes make a programmatic commits.... patrick View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3935991#3935991 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3935991 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
