[ https://jira.jboss.org/jira/browse/JBSEAM-3961?page=com.atlassian.jira.pl... ] John Gilbert commented on JBSEAM-3961: -------------------------------------- i hear you. this is just not the behavior i expected. may be it just needs to be documented if not already... i noticed it when i was trying to improve performance by leveraging @Out instead of relying on getters which get called many times. some of these getters rely on an entityManager which is closed on destroy, so I was getting exceptions. so far I am handling this by checking if the entityManager is still open. maybe there is a better way... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3961?page=com.atlassian.jira.pl... ] John Gilbert commented on JBSEAM-3961: -------------------------------------- Looks like a solution already exists. Just add @BypassInterceptors @Destroy @Remove @BypassInterceptors public void destroy() { } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira