[JBoss JIRA] (ISPN-11620) Remove EncoderRegistry from DataConversion
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-11620?page=com.atlassian.jira.plugi... ]
Work on ISPN-11620 started by Gustavo Fernandes.
------------------------------------------------
> Remove EncoderRegistry from DataConversion
> -------------------------------------------
>
> Key: ISPN-11620
> URL: https://issues.redhat.com/browse/ISPN-11620
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 11.0.0.Dev03
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> The DataConversion carries an instance of EncodingRegistry, and exports operations that use it internally:
> * isConversionSupported(MediaType mediaType)
> * convert(Object o, MediaType from, MediaType to)
> * convertToRequestFormat(Object o, MediaType contentType)
> Those operations should be removed and moved to the EncoderRegistry itself, freeing the DataConversion objects from maintaining an internal reference to the registry. This also solves the issue of static DataContainer objects being used in mulitple nodes in the same JVM
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-11620) Remove EncoderRegistry from DataConversion
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-11620?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-11620:
-------------------------------------
Description:
The DataConversion carries an instance of EncodingRegistry, and exports operations that use it internally:
* isConversionSupported(MediaType mediaType)
* convert(Object o, MediaType from, MediaType to)
* convertToRequestFormat(Object o, MediaType contentType)
Those operations should be removed and moved to the EncoderRegistry itself, freeing the DataConversion objects from maintaining an internal reference to the registry. This also solves the issue of static DataContainer objects being used in mulitple nodes in the same JVM
was:
The DataConversion carries an instance of EncodingRegistry, and exports operations that use it internally:
* isConversionSupported(MediaType mediaType)
* convert(Object o, MediaType from, MediaType to)
* convertToRequestFormat(Object o, MediaType contentType)
Those operations should be removed and moved to the EncoderRegistry itself, freeing the DataConversion objects from maintaining an internal reference to the registry. This also solves the issue of static DataContainer objects being used in mulitple nodes in the same JVM keeping reference to this field internally.
> Remove EncoderRegistry from DataConversion
> -------------------------------------------
>
> Key: ISPN-11620
> URL: https://issues.redhat.com/browse/ISPN-11620
> Project: Infinispan
> Issue Type: Bug
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> The DataConversion carries an instance of EncodingRegistry, and exports operations that use it internally:
> * isConversionSupported(MediaType mediaType)
> * convert(Object o, MediaType from, MediaType to)
> * convertToRequestFormat(Object o, MediaType contentType)
> Those operations should be removed and moved to the EncoderRegistry itself, freeing the DataConversion objects from maintaining an internal reference to the registry. This also solves the issue of static DataContainer objects being used in mulitple nodes in the same JVM
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-11620) Remove EncoderRegistry from DataConversion
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-11620?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-11620:
-------------------------------------
Status: Open (was: New)
> Remove EncoderRegistry from DataConversion
> -------------------------------------------
>
> Key: ISPN-11620
> URL: https://issues.redhat.com/browse/ISPN-11620
> Project: Infinispan
> Issue Type: Bug
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> The DataConversion carries an instance of EncodingRegistry, and exports operations that use it internally:
> * isConversionSupported(MediaType mediaType)
> * convert(Object o, MediaType from, MediaType to)
> * convertToRequestFormat(Object o, MediaType contentType)
> Those operations should be removed and moved to the EncoderRegistry itself, freeing the DataConversion objects from maintaining an internal reference to the registry. This also solves the issue of static DataContainer objects being used in mulitple nodes in the same JVM keeping reference to this field internally.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-11620) Remove EncoderRegistry from DataConversion
by Gustavo Fernandes (Jira)
Gustavo Fernandes created ISPN-11620:
----------------------------------------
Summary: Remove EncoderRegistry from DataConversion
Key: ISPN-11620
URL: https://issues.redhat.com/browse/ISPN-11620
Project: Infinispan
Issue Type: Bug
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
The DataConversion carries an instance of EncodingRegistry internally, and exports operations that use it internally:
* isConversionSupported(MediaType mediaType)
* convert(Object o, MediaType from, MediaType to)
* convertToRequestFormat(Object o, MediaType contentType)
Those operations should be removed and moved to the EncoderRegistry itself, freeing the DataConversion objects from maintaining an internal reference to the registry. This also solves the issue of static DataContainer objects being used in mulitple nodes in the same JVM keeping reference to this field internally.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-11620) Remove EncoderRegistry from DataConversion
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-11620?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-11620:
-------------------------------------
Description:
The DataConversion carries an instance of EncodingRegistry, and exports operations that use it internally:
* isConversionSupported(MediaType mediaType)
* convert(Object o, MediaType from, MediaType to)
* convertToRequestFormat(Object o, MediaType contentType)
Those operations should be removed and moved to the EncoderRegistry itself, freeing the DataConversion objects from maintaining an internal reference to the registry. This also solves the issue of static DataContainer objects being used in mulitple nodes in the same JVM keeping reference to this field internally.
was:
The DataConversion carries an instance of EncodingRegistry internally, and exports operations that use it internally:
* isConversionSupported(MediaType mediaType)
* convert(Object o, MediaType from, MediaType to)
* convertToRequestFormat(Object o, MediaType contentType)
Those operations should be removed and moved to the EncoderRegistry itself, freeing the DataConversion objects from maintaining an internal reference to the registry. This also solves the issue of static DataContainer objects being used in mulitple nodes in the same JVM keeping reference to this field internally.
> Remove EncoderRegistry from DataConversion
> -------------------------------------------
>
> Key: ISPN-11620
> URL: https://issues.redhat.com/browse/ISPN-11620
> Project: Infinispan
> Issue Type: Bug
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> The DataConversion carries an instance of EncodingRegistry, and exports operations that use it internally:
> * isConversionSupported(MediaType mediaType)
> * convert(Object o, MediaType from, MediaType to)
> * convertToRequestFormat(Object o, MediaType contentType)
> Those operations should be removed and moved to the EncoderRegistry itself, freeing the DataConversion objects from maintaining an internal reference to the registry. This also solves the issue of static DataContainer objects being used in mulitple nodes in the same JVM keeping reference to this field internally.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (IPROTO-139) Cascading serialization contexts
by Nistor Adrian (Jira)
Nistor Adrian created IPROTO-139:
------------------------------------
Summary: Cascading serialization contexts
Key: IPROTO-139
URL: https://issues.redhat.com/browse/IPROTO-139
Project: Infinispan ProtoStream
Issue Type: Enhancement
Affects Versions: 4.4.0.Alpha1
Reporter: Nistor Adrian
Marshaller and type lookups that cannot be resolved in the current context should be delegated/cascaded to another context (if specified). A tree of such contexts should be able to exist, providing more separation that just the package based namespace, for advanced usages.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (IPROTO-139) Cascading serialization contexts
by Nistor Adrian (Jira)
[ https://issues.redhat.com/browse/IPROTO-139?page=com.atlassian.jira.plugi... ]
Nistor Adrian reassigned IPROTO-139:
------------------------------------
Assignee: Nistor Adrian
> Cascading serialization contexts
> --------------------------------
>
> Key: IPROTO-139
> URL: https://issues.redhat.com/browse/IPROTO-139
> Project: Infinispan ProtoStream
> Issue Type: Enhancement
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
>
> Marshaller and type lookups that cannot be resolved in the current context should be delegated/cascaded to another context (if specified). A tree of such contexts should be able to exist, providing more separation that just the package based namespace, for advanced usages.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years