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/08 19:21:50 UTC
[jira] Created: (TAPESTRY-1891) Tapestry IoC Service Proxies should
be serializable
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
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
[jira] Assigned: (TAPESTRY-1891) Tapestry IoC Service Proxies
should be serializable
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ 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
[jira] Commented: (TAPESTRY-1891) Tapestry IoC Service Proxies
should be serializable
Posted by "Massimo Lusetti (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541167 ]
Massimo Lusetti commented on TAPESTRY-1891:
-------------------------------------------
This would be neat!
> 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
>
> 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
[jira] Commented: (TAPESTRY-1891) Tapestry IoC Service Proxies
should be serializable
Posted by "Ognen Ivanovski (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542380 ]
Ognen Ivanovski commented on TAPESTRY-1891:
-------------------------------------------
+1 Recently I had a conference presentation that tried to tackle this same problem on more or less the same way. http://jazoon.com/download/presentations/866.pdf
> 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
>
> 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
[jira] Closed: (TAPESTRY-1891) Tapestry IoC Service Proxies should
be serializable
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-1891.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.7
> 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
> Fix For: 5.0.7
>
>
> 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