[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4002) InstantiationException at Stateful bean (Could not instantiate Seam component)
Norman Richards (JIRA)
jira-events at lists.jboss.org
Tue Mar 10 15:59:25 EDT 2009
[ https://jira.jboss.org/jira/browse/JBSEAM-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12456527#action_12456527 ]
Norman Richards commented on JBSEAM-4002:
-----------------------------------------
I am 99.99% sure this is a problem with your packaging and not a Seam issue. If you can post a deployable project that demonstrates the error or a specific modification to an existing application, I'll take a look just to verify it's not Seam. Otherwise, I'm going to have to chalk this up as problem with your project.
> InstantiationException at Stateful bean (Could not instantiate Seam component)
> ------------------------------------------------------------------------------
>
> Key: JBSEAM-4002
> URL: https://jira.jboss.org/jira/browse/JBSEAM-4002
> Project: Seam
> Issue Type: Bug
> Components: EJB3
> Affects Versions: 2.1.1.CR2, 2.1.1.GA
> Environment: JBoss AS 4.2.2 / 4.2.3 / 5.0.0, WinXP / Debian Linux, JD1.6 update 7/11/12
> Reporter: Tamas Malatinszki
>
> Stateful beans are failing with "Could not instantiate Seam component" error in Seam 2.1.1 CR2 and above. The root cause is "java.lang.ClassNotFoundException: No ClassLoaders found for: <stateful bean>". The application is working fine with Seam 2.1.1 CR1 (and before).
> See the whole stacktrace and the related code at http://www.seamframework.org/Community/StatefulBeanErrorInSeam211GAAndCR2
--
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