[ https://issues.jboss.org/browse/SEAMPERSIST-80?page=com.atlassian.jira.pl... ] Fab Mars updated SEAMPERSIST-80: -------------------------------- Description: When Seam Persistence/transaction is installed and calling from a SERVLET an EJB business method that performs em.persist/merge, tranasaction management is gone, thus statements are not executed. I read carefully these: http://docs.jboss.org/seam/3/persistence/latest/reference/en-US/html/pers... ??By default seam will attempt to look up java:comp/UserTransaction from JNDI *(or alternatively retrieve it from the EJBContext if a container managed transaction is active)*.?? ==>This is obviously not correct if you try with the attached example. I tried to use a SMPC, to no avail. Then I read this https://community.jboss.org/thread/178844 Without much hope, I tired to use ?cid=#{conversation.id} witht he servelt URL, to no avail. was: When Seam Persistence/transaction is installed and calling from a SERVLET an EJB business method that performs em.persist/merge, tranasaction management is gone, thus statements are not executed. I read carefully these: http://docs.jboss.org/seam/3/persistence/latest/reference/en-US/html/pers... [i]By default seam will attempt to look up java:comp/UserTransaction from JNDI [b](or alternatively retrieve it from the EJBContext if a container managed transaction is active)[/b].[/i] ==>This is obviously not correct if you try with the attached example. I tried to use a SMPC, to no avail. Then I read this https://community.jboss.org/thread/178844 Without much hope, I tired to use ?cid=#{conversation.id} witht he servelt URL, to no avail. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira