Occasionally, I'll have a data object that stores a reference to
service. Here's an example:
public class ActiveUser extends BaseOptimizedSessionPersistedObject
{
private long userId;
private final Session session;
public ActiveUser(Session session)
{
this.session = sess
Thanks Howard.
We have few Tapestry applications running in the same server. (and planning
to have more)
I am assuming it is going to cause issues based on your reply. What is the
best way to avoid this issue?
Just curious, at what point does a service(/proxy) gets
serialized/de-serialized? I am
If you have only one Tapestry application, you can safely ignore this warning.
It's related to the code that allows services to be serialized (that
is, the service proxies are serializable even though the services
themselves are not). When a service is de-serialized, there's a static
variable used
