I've been trying to figure this bug out and might have come across some useful information...
I noticed that whenever I did *not* define a method for a stateful bean that had the @Remove @Destroy annotations, I could load the JSF page that referenced it once and each subsequent refresh caused the "Transaction already active." I realize that this is definitely defined in the manual, but I am unsure if the lack of a destroy method should hang Seam, requiring a restart. Not too sure if that helps at all. - Cory View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3930778#3930778 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3930778 ------------------------------------------------------- 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
