Hi Frank, I don't know how much of this you already know, but here goes. t:saveState is pointed at one value on the "EL landscape". It calls getValue() in the last phase of request x and setValue() on the first phase of request x + 1 . The value is transported between requests using java serialization, which has nothing to do w/ the Spring DI engine.
Why do you get startup errors? Dennis Byrne >-----Original Message----- >From: Frank Russo [mailto:[EMAIL PROTECTED] >Sent: Friday, August 18, 2006 02:00 PM >To: 'MyFaces Discussion' >Subject: Anyone using t:saveState on beans with Spring objects injected > >I having issue using t:saveState on beans with spring classes. If I >implement Serializable on my Spring classes I get startup errors, so I >had to set the spring objects as transient in my beans. On a new >request, though, the spring classes are null, so they are not getting >injected the second time through. > >Does anyone have this working? If so, how did you configure it? > >Thanks... > >Frank Russo >Senior Developer >FX Alliance, LLC > >
