[infinispan-issues] [JBoss JIRA] (ISPN-1367) Make JBoss Marshalling class resolver configurable

[Galder Zamarreño (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Galder Zamarreño updated ISPN-1367:
-----------------------------------

          Summary: Make JBoss Marshalling class resolver configurable  (was: Add SPI which can be used to attach extra info to a serialized data and callback when data is deserialized)
    Fix Version/s: 5.2.0.ALPHA1
      Description: 
JBoss Marshalling's class resolver should be configurable in order to enable the following use case and to help with classloading in a modular environment:

In an environment such as JBoss AS, where there is some sort of consistent identification of deployments across nodes (i.e. a deployment id) this SPI can be used to attach the deployment id to the serialized data, and then on deserialization used to locate the correct classloader to use

  was:In an environment such as JBoss AS, where there is some sort of consistent identification of deployments across nodes (i.e. a deployment id) this SPI can be used to attach the deployment id to the serialized data, and then on deserialization used to locate the correct classloader to use


    
> Make JBoss Marshalling class resolver configurable
> --------------------------------------------------
>
>                 Key: ISPN-1367
>                 URL: https://issues.jboss.org/browse/ISPN-1367
>             Project: Infinispan
>          Issue Type: Feature Request
>    Affects Versions: 5.0.0.FINAL
>            Reporter: Pete Muir
>            Assignee: Galder Zamarreño
>             Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL
>
>         Attachments: chat.txt
>
>
> JBoss Marshalling's class resolver should be configurable in order to enable the following use case and to help with classloading in a modular environment:
> In an environment such as JBoss AS, where there is some sort of consistent identification of deployments across nodes (i.e. a deployment id) this SPI can be used to attach the deployment id to the serialized data, and then on deserialization used to locate the correct classloader to use

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira