[
https://issues.jboss.org/browse/ISPN-10452?page=com.atlassian.jira.plugin...
]
Gustavo Fernandes updated ISPN-10452:
-------------------------------------
Description:
The JSON rendering currently is based on inspecting Attributes in Configuration(Builder)
class, and it's also possible to plug-in an AttributeSerializer that will emit the
Attribute as a JSON Object rather than a field (property name/value pair) inside a JSON
object.
Sometimes it's not always clear what will be the rendered JSON when attributes can be
objects and vice-versa, so JSON objects should be generated from Configuration objects and
JSON fields should be generated from the Configuration's Attributes.
was:
The JSON rendering currently is based on inspecting Attributes in Configuration(Builder)
class, and it's also possible to plug-in an AttributeSerializer that will emit the
Attribute as a JSON object rather than a field inside a JSON object.
For the sake of simplicity and less mental gymnastics, JSON objects should be generated
from Configuration objects and JSON fields should be generated from the
Configuration's Attributes collections.
Remove AsElementAttributeSerializer
-----------------------------------
Key: ISPN-10452
URL:
https://issues.jboss.org/browse/ISPN-10452
Project: Infinispan
Issue Type: Bug
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
Priority: Major
The JSON rendering currently is based on inspecting Attributes in Configuration(Builder)
class, and it's also possible to plug-in an AttributeSerializer that will emit the
Attribute as a JSON Object rather than a field (property name/value pair) inside a JSON
object.
Sometimes it's not always clear what will be the rendered JSON when attributes can be
objects and vice-versa, so JSON objects should be generated from Configuration objects and
JSON fields should be generated from the Configuration's Attributes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)