Return-Path: 
 <users-return-28767-apmail-myfaces-users-archive=myfaces.apache.org@myfaces.apache.org>
Delivered-To: apmail-myfaces-users-archive@www.apache.org
Received: (qmail 72988 invoked from network); 25 Sep 2006 16:53:46 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 25 Sep 2006 16:53:46 -0000
Received: (qmail 9738 invoked by uid 500); 25 Sep 2006 16:53:27 -0000
Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org
Received: (qmail 9688 invoked by uid 500); 25 Sep 2006 16:53:27 -0000
Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@myfaces.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@myfaces.apache.org>
List-Post: <mailto:users@myfaces.apache.org>
List-Id: <users.myfaces.apache.org>
Reply-To: "MyFaces Discussion" <users@myfaces.apache.org>
Delivered-To: mailing list users@myfaces.apache.org
Received: (qmail 9639 invoked by uid 99); 25 Sep 2006 16:53:26 -0000
Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org)
 (140.211.166.84)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Sep 2006 09:53:26 -0700
Authentication-Results: idunn.apache.osuosl.org
 smtp.mail=mailing-lists@dueppe.com; spf=permerror
X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=
Received-SPF: error (idunn.apache.osuosl.org: domain dueppe.com from
 83.137.96.25 cause and error)
Received: from [83.137.96.25] ([83.137.96.25:39232] helo=pm1.terions.de)
	by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP
	id DE/6C-13750-D6908154 for <users@myfaces.apache.org>;
 Mon, 25 Sep 2006 09:53:03 -0700
Received: (qmail 29863 invoked by uid 98); 25 Sep 2006 16:52:05 -0000
Received: from muedsl-82-207-221-084.citykom.de (HELO ?192.168.123.100?)
 (mailing-lists@dueppe.com@82.207.221.84)
  by pm1.terions.de with SMTP; 25 Sep 2006 16:52:05 -0000
Message-ID: <4518091D.1050905@dueppe.com>
Date: Mon, 25 Sep 2006 18:51:41 +0200
From: =?ISO-8859-15?Q?Ingo_D=FCppe?= <mailing-lists@dueppe.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: MyFaces Discussion <users@myfaces.apache.org>
Subject: managed-beans, spring references, and serializable
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Hi,

I have a conceptional question. Within my application I define a 
managed-bean "registrationController" that gets a reference to a spring 
bean "registrationService" by the jsf property injection. The spring 
bean is stateless and is not serializable, so I need to define the field 
reference in "registrationController" as transient. This prevents me for 
getting NotSerializableException.

But what happens if the session is reloaded, will jsf reinject the 
properties?
Is there any recommended way how to deal with this.

The obvious way to make the service bean serializable doesn't seem to 
work, because a whole data access layer is bound to the service bean.

Or do I need to clearly separate. All managed-beans that have a 
reference to the service layer need to be scoped as application (or 
maybe as request) and only the value objects or entities are allowed to 
be stored in the session scope.

Regards,
Ingo

Here is an example of my configuration:
    <managed-bean>
        <managed-bean-name>registrationController</managed-bean-name>
        
<managed-bean-class>org.openuss.security.registration.RegistrationController</managed-bean-class>
        <managed-bean-scope>session</managed-bean-scope>
        <managed-property>
            <property-name>service</property-name>
            <value>#{registrationService}</value>
        </managed-property>
    </managed-bean>