[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3757) TypeNotPresentException: Type javax.ejb.Stateful not present in POJO mode (ie non ejb3..)
[
https://jira.jboss.org/jira/browse/JBSEAM-3757?page=com.atlassian.jira.pl...
]
Denis Forveille commented on JBSEAM-3757:
-----------------------------------------
Thanks for the explanation (and the fix!).
Our app with Seam v2.1.1 CR1 now starts with the fix in WAS v6.1.0.17 in POJOs mode...
About the annotation thing, maybe you coudl have a look at JBSEAM-3726. This is another
JIRA I opened but this time with WebSphere v7.0 (JEE5+EJB3 as we are trying to move our
app to this version of WAS and get the benefits of EJB3 and seam....)
This *may* be another example of handling differently annotations between servers/jdk,
even if I think that JBSEAM-3726 is more about a different implementation/interpreation of
the JEE5 API in WAS than a difference in the JDKs .
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