[seam-issues] [JBoss JIRA] (SEAMPERSIST-80) CMT vanishes when using Servlets and Seam Transaction

[Fab Mars (JIRA)]

     [ https://issues.jboss.org/browse/SEAMPERSIST-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fab Mars updated SEAMPERSIST-80:
--------------------------------

    Summary: CMT vanishes when using Servlets and Seam Transaction  (was: CMT vanishes when using Servlets and Seam Transaction/Persistence)

    
> CMT vanishes when using Servlets and Seam Transaction
> -----------------------------------------------------
>
>                 Key: SEAMPERSIST-80
>                 URL: https://issues.jboss.org/browse/SEAMPERSIST-80
>             Project: Seam Persistence
>          Issue Type: Bug
>    Affects Versions: 3.1.0.Final
>         Environment: Win7, Glassfish 3.1.2.2, Mojarra 2.1.14, Weld 1.1.8, Seam 3.1.0
>            Reporter: Fab Mars
>              Labels: cmt, ejb, seam, servlet, transaction
>         Attachments: TestEjbWeb.zip
>
>
> 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/persistence.html#d0e68
> ??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} with the servlet 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