[
https://issues.jboss.org/browse/WELD-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko Lukša resolved WELD-537.
------------------------------
Fix Version/s: (was: 1.2.0.Beta1)
Resolution: Duplicate Issue
Apparently this was already taken care of.
I've tested all the possibilities and get the correct error message in all of
them.
See validators_en.messages:
{code}
PASSIVATING_BEAN_WITH_NONSERIALIZABLE_INTERCEPTOR=The bean {0} declared a
passivating scope but has a non-serializable interceptor {1}
PASSIVATING_BEAN_WITH_NONSERIALIZABLE_DECORATOR=The bean {0} declared a
passivating scope but has non-serializable decorator {1}
{code}
> More details to WELD-000072 Managed bean declaring a passivating scope must
> be passivation capable.
> ---------------------------------------------------------------------------------------------------
>
> Key: WELD-537
> URL: https://issues.jboss.org/browse/WELD-537
> Project: Weld
> Issue Type: Feature Request
> Components: Class Beans (Managed and Session)
> Affects Versions: 1.0.1.Final
> Reporter: Nicklas Karlsson
> Assignee: Marko Lukša
>
> The error message should be more detailed, currently
> ManagedBean.initializeAfterBeanDiscovery can have multiple conditions that
> set the passivationCapableBean to false (non-serializable interceptors etc)
> but it's hard to tell exactly what is wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
