You don't have to mark your field as transient. The proxy is indeed serializable (at least the object that it writeReplaces itself with is) and will re-establish itself upon deserialization.
On Tue, Jul 29, 2008 at 4:11 AM, Gerald Reinhart <[EMAIL PROTECTED]> wrote: > > > jwcarman wrote: >> >> Why are you doing this again? @SpringBean already takes care of >> re-establishing the connection upon deserialization. >> > > Are you sure ? > > > Sebastiaan van Erk wrote: >> >> The myService field is filled with a proxy to the service which is >> serializable and can look up >> the service again if it is lost (due to a serialize/deserialize cycle of >> the component). The proxy is injected on instantiation of the component >> and NOT on deserialization (see also IComponentInstantiationListener). >> >> Marking it transient will not work because after deserialize the >> myService field will be null, calling all subsequent calls to the >> service to fail with a NullPointerException. >> > > -- > View this message in context: > http://www.nabble.com/%40SpringBean-and-serialization-tp15330505p18707368.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
