[cdi-dev] [JBoss JIRA] (CDI-708) Serialization problems in section "1.3.1. JSF example".

[Martin Kouba (JIRA)]

    [ https://issues.jboss.org/browse/CDI-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421502#comment-13421502 ] 

Martin Kouba commented on CDI-708:
----------------------------------

Good catch! For the record, this also applies to {{CriteriaQuery<User> query}} field and  the resource bean for {{EntityManager}} is defined in 1.3.3 as {{@Dependent}}:
{code:java}
 @Produces @PersistenceContext(unitName="UserData")
 @Users EntityManager userDatabaseEntityManager;
{code}
(in fact, containers are not required to support resources with scope other than {{@Dependent}})

> Serialization problems in section "1.3.1. JSF example".
> -------------------------------------------------------
>
>                 Key: CDI-708
>                 URL: https://issues.jboss.org/browse/CDI-708
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Concepts
>    Affects Versions: 2.0 .Final
>            Reporter: Martin Andersson
>
> Section "1.3.1. JSF example" provide an example of a class {{Login}}, that saves in its state an {{EntityManager}} reference and two {{Parameter}} references.
> The JPA specification does not say that a {{Parameter}} instance is serializable.
> This is also true for the {{EntityManager}} reference which is {{@Dependent}} (see section "1.3.3. Java EE component environment example"). JPA does not specify that the {{EntityManager}} is serializable and the EJB specification only specifies serialization semantics for passivation-enabled {{@Stateful}} EJB:s (which encourages the bean provider to not mark an {{EntityManager}} reference as transient, see EJB §4.2.1).



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)