[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 fix I'll test it today
However, the question is why this class (EjbSynchronizations) has been loaded in first
place?
As I've not declared "<transaction:ejb-transaction>", the classes
related to EJB3 should not be loaded nor scanned at all. Is it because of some
dependencies on this class6 in thsi class, it is strange that a class depends on a class
that *need* EJB3 while not in EJB3 mode...
IMHO, i think that the problem is more general than silently ignoring classloder
exceptiosn there...
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