"ellenzhao" wrote : | The concrete error messages I got were always something like "no transaction available"
Well, you could always manually get a transaction with Transaction.instance() and begin/commit. But probably the right way is marking the method as needing a transaction. If it's a javabean component, you could use @Transactional. I don't know much how Ejb works, but I imagine there's a way you can tell the container it needs a transaction, too. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064195#4064195 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064195 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
