[
https://jira.jboss.org/jira/browse/JBSEAM-3757?page=com.atlassian.jira.pl...
]
Denis Forveille updated JBSEAM-3757:
------------------------------------
Attachment: traces_ComponentDeploymentHandler.txt
components.xml
Dan, you were right, this is org.jboss.seam.transaction.EjbSynchronizations that is the
problem, an no, there is no "<transaction:ejb-transaction>" in our
component.xml
I uploaded the trace and our component.xml
thanks
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: 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