Hi all,
Could someone from the EJB-container-team verify the answer? (see
below) It would mean - I have to ensure that a proxy to an EJB is
serializable, or couldn't inject EJBs into a view-scoped backing bean...
thanks!,
adam
Begin forwarded message:
> From: rlubke_at_dev.java.net
> Date: 28. Oktober 2009 21:10:05 MEZ
> To: abien_at_dev.java.net
> Subject: [Issue 10466] [jsf] Problematic Serialization Attempt Of
> EJB 3.1 in Backing Bean
>
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=10466
>
>
>
> User rlubke changed the following:
>
> What |Old value |New value
> =
> =
> =
> =
> =
> =
> =
> =
> =
> =
> ======================================================================
> Status|REOPENED |RESOLVED
> --------------------------------------------------------------------------------
> Resolution| |INVALID
> --------------------------------------------------------------------------------
>
>
>
>
> ------- Additional comments from rlubke_at_dev.java.net Wed Oct 28
> 20:10:01 +0000 2009 -------
> Like I said, this is a warning that you're putting an object into
> scope that
> *may* be serialized. It's up to you to ensure that if it's
> acceptable that such
> an object can be serialized to make is Serializable. If the object
> shouldn't be
> serialized then you shouldn't put it into scope or ensure you're
> running in a
> configuration where the object could be serialized (i.e. client
> state saving,
> clustered environment, containers that serialize the session on
> shutdown, etc.).
Consultant, Author, Speaker, Java Champion
Weblog: blog.adam-bien.com
press: press.adam-bien.com
eMail: abien_at_adam-bien.com
twitter: twitter.com/adambien
Mobile: 0049(0)170 280 3144
Author: 7 (Java SE/EE, SOA) Books, about 100 articles