You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2007/11/16 20:39:43 UTC
[jira] Assigned: (TAPESTRY-1891) Tapestry IoC Service Proxies
should be serializable
[ https://issues.apache.org/jira/browse/TAPESTRY-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAPESTRY-1891:
----------------------------------------------
Assignee: Howard M. Lewis Ship
> Tapestry IoC Service Proxies should be serializable
> ---------------------------------------------------
>
> Key: TAPESTRY-1891
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1891
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.0.7
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> In HiveMind, the services proxies were serializable, and this is a useful feature for Tapestry IoC as well. The outer proxy should implement Externalizable and write a token into the stream; the token includes the service id. When the token is deserialized, it uses the service id to reconstitute the same (or equivalent) proxy. In this way, data objects that hold references to services can be serialized, or even transferred over RMI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org