[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3757) TypeNotPresentException: Type javax.ejb.Stateful not present in POJO mode (ie non ejb3..)
Dan Allen (JIRA)
jira-events at lists.jboss.org
Wed Nov 26 15:34:36 EST 2008
[ https://jira.jboss.org/jira/browse/JBSEAM-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12440007#action_12440007 ]
Dan Allen commented on JBSEAM-3757:
-----------------------------------
Could you please put a log statement in the line org.jboss.seam.deployment.ComponentDeploymentHandler.postProcess(ComponentDeploymentHandler.java:59) so that we know which component class is being processed? Also, can you verify that you do not have <transaction:ejb-transaction> in your component descriptor. Clearly what is happening is that a component with a @Stateful annotation is being processed. My guess is EjbSynchronizations, but perhaps not.
> TypeNotPresentException: Type javax.ejb.Stateful not present in POJO mode (ie non ejb3..)
> -----------------------------------------------------------------------------------------
>
> Key: JBSEAM-3757
> URL: https://jira.jboss.org/jira/browse/JBSEAM-3757
> Project: Seam
> Issue Type: Bug
> Affects Versions: 2.1.1.CR1
> Environment: WebSphere v6.1.0.17 in POJO mode (ie non EJB3)
> Reporter: Denis Forveille
> Priority: Blocker
> Fix For: 2.1.1.CR2
>
> Attachments: traceback.txt
>
>
> The application does not start with seam v2.1.1.CR1 due to a "java.lang.TypeNotPresentException: Type javax.ejb.Stateful not present" exception
> It seems that seams tries to locate (again...) some ejb3 classes not present when seam is used in pojo mode in a non-ejb3 environnement
> See the attached traceback
--
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
More information about the seam-issues
mailing list