[seam-issues] [JBoss JIRA] (SEAMTRANSACTION-18) DefaultSeamTransaction relies on EJB-API but probably shouldn't

Geoffrey De Smet (JIRA) jira-events at lists.jboss.org
Mon Oct 8 12:12:03 EDT 2012

    [ https://issues.jboss.org/browse/SEAMTRANSACTION-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724775#comment-12724775 ] 

Geoffrey De Smet commented on SEAMTRANSACTION-18:

In case it helps: instead of adding ejb-api.jar to the classpath, I fixed this by adding weld-core and weld-se-core to the classpath (but not the shaded weld-se).
> DefaultSeamTransaction relies on EJB-API but probably shouldn't
> ---------------------------------------------------------------
>                 Key: SEAMTRANSACTION-18
>                 URL: https://issues.jboss.org/browse/SEAMTRANSACTION-18
>             Project: Seam Transaction
>          Issue Type: Feature Request
>    Affects Versions: 3.1.0.Final
>         Environment: Jave SE
>            Reporter: Wulf Rowek
>            Assignee: Stuart Douglas
> trying to use the DefaultSeamTransaction w/o ejb-api.jar on classpath leads to this error:
> INFO: WELD-000119 Not generating any bean definitions from org.jboss.seam.transaction.DefaultSeamTransaction because of underlying class loading error
> Caused by: java.lang.NoClassDefFoundError: javax/ejb/EJBContext
> adding ejb-api as a workaround is not an option cause seam persistence uses existing ejb-classpath-entries for detecting an ee-environment.
> hence you'll get an unexpected seam persistence behaviour in a non-ee env with ejb-api on classpath, like described here: https://community.jboss.org/message/715541#715541

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

More information about the seam-issues mailing list