[forge-dev] [JBoss JIRA] Commented: (SEAMFORGE-34) @Transactional is used by scaffold plugin while not available yet

Marek Schmidt (JIRA) jira-events at lists.jboss.org
Wed Mar 30 04:53:37 EDT 2011

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

Marek Schmidt commented on SEAMFORGE-34:

The problem seems to be that org.jboss.seam.persistence.transaction.Transactional has been moved to org.jboss.seam.transaction.Transactional between seam persistence beta and final. A workaround for this bug would be to:

1. change the import to org.jboss.seam.transaction.Transactional
2. change the interceptor in beans.xml to org.jboss.seam.transaction.TransactionInterceptor

> @Transactional is used by scaffold plugin while not available yet
> -----------------------------------------------------------------
>                 Key: SEAMFORGE-34
>                 URL: https://issues.jboss.org/browse/SEAMFORGE-34
>             Project: Seam Forge
>          Issue Type: Bug
>            Reporter: Paul Bakker
>            Priority: Minor
> I did the following:
> -create project
> -install jpa, jsf and cdi
> -create entity
> -install scaffold
> -scaffold from entity...
> The generated code uses @Transactional which is not available on the project yet. The scaffold plugin should check this and add missing facets.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the forge-dev mailing list