[ https://issues.jboss.org/browse/IPROTO-56?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated IPROTO-56: ------------------------------------ Description: The use case is a class that describe the entity. This class contains a 'type' and a list of properties. MarshallerProvider is used to associate a type with a marshaller that uses this 'type' to understand the fields and data types to read/write the stream. The type of the entity is contained in the entity itself, and when reading from the stream, this type is used to figure out the fields to read. During writes, though, the type is not involved so it's not possible to use the same strategy. Attached is a unit test to illustrate the situation. This is not necessarily a bug, it may be possible to achieve the usage of Dynamic Entities under other circumstances, or maybe the API needs to be extended. was: The use case is there is a class that describe the entity, which contains a 'type' and a list of properties. MarshallerProvider is used to associate a type with a marshaller that uses that 'type' to read/write The type of entity is contained in the entity itself, and when reading from the stream, this type is used to figure out the fields to read. During writes, though, the type is not involved so it's not possible to use the same strategy. Attached is a unit test to illustrate the situation. This is not necessarily a bug, it may be possible to achieve the usage of Dynamic Entities under other circumstances, or maybe the API needs to be extended. -- This message was sent by Atlassian JIRA (v7.5.0#75005)