[
https://issues.jboss.org/browse/JBIDE-3126?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-3126:
--------------------------------------------
wether warning or error - it all depends on what happens at runtime.
i.e. for @SessionScoped non serializable the deployment simply errors thus in that case
Error seems appropriate as default, not sure if the others might just have unexpected
behavior and thus is better of with a Warning.
Raise it on the weld list/irc for feedback I would say.
Validate the serializability of beans injected into
passivating-scoped beans.
-----------------------------------------------------------------------------
Key: JBIDE-3126
URL:
https://issues.jboss.org/browse/JBIDE-3126
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: cdi (jsr-299)
Reporter: Max Rydahl Andersen
Assignee: Alexey Kazakov
Labels: new_and_noteworthy
Fix For: 3.2.1, 3.3.0.M1
So what we can verify here:
If the bean belongs to @SessionScoped or @ConversationScope or to any
@NormalScope(passivating=true)
and the bean is not @Stateful then we should check if the bean implements
java.io.Serializible.
If so then ok otherwise we mark it as an error (or warning by default?).
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira