[
https://issues.jboss.org/browse/WELD-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated WELD-867:
----------------------------------
Priority: Major (was: Blocker)
i lower the priority because with weld 1.1 we can use a fallback (serialization
of the bean-id + BeanManager#getPassivationCapableBean for restoring the bean)
and it looks like the CreationalContext of weld 1.1 is ok. however, since it
isn't difficult to do the same inside of bean implementations, it's still a
good idea to make the implementations serializable.
> bean implementations should be serializable
> -------------------------------------------
>
> Key: WELD-867
> URL: https://issues.jboss.org/browse/WELD-867
> Project: Weld
> Issue Type: Feature Request
> Components: Built-in beans, Clustering, Scopes & Contexts
> Affects Versions: 1.1.0.Final
> Reporter: Gerhard Petracek
> Fix For: 1.2.0.CR1
>
>
> for custom scope implementations it's required that beans are serializable.
> -> one of the following classes should implement java.io.Serializable
> https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/weld/bean/RIBean.java
> https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/weld/bean/AbstractBean.java
> https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/weld/bean/ManagedBean.java
--
This message is automatically generated by JIRA.
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
