[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3757) TypeNotPresentException: Type javax.ejb.Stateful not present in POJO mode (ie non ejb3..)

[Dan Allen (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBSEAM-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12441014#action_12441014 ] 

Dan Allen commented on JBSEAM-3757:
-----------------------------------

This issue can be tested by deploying the JPA example for the Seam distribution to Tomcat running with the IBM JVM and the ejb-api-2.1.jar on the classpath (either the Tomcat shared classpath or WEB-INF/lib).

> 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
>          Components: Core
>    Affects Versions: 2.1.1.CR1
>         Environment: WebSphere v6.1.0.17 in POJO mode (ie non EJB3)
>            Reporter: Denis Forveille
>            Assignee: Dan Allen
>            Priority: Blocker
>             Fix For: 2.1.1.CR2
>
>         Attachments: components.xml, traceback.txt, traces_ComponentDeploymentHandler.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