Re: FC-250

[Shawn McKinney]

Hey Chris,

Changes made by Kiran to support a JSON message format via Fortress REST 
component.

JSON is used by the new UI, Embrasure.

Obviously if this is breaking some previous behavior we need to provide a 
solution.

Can you elaborate on the problem… you mentioned serialization, what is the 
scenario that worked before that no longer works?

Thanks,
—Shawn

> On Dec 19, 2018, at 2:10 PM, Pike, Christopher <clp...@psu.edu> wrote:
> 
> This commit is a potentially breaking change. 
> (https://github.com/apache/directory-fortress-core/commit/2d8a53071b8d8b5bb3b6256f084a9e12d4a7cc10#diff-280616e1526a17336cdb4ff1855d7439)
> 
> 
> Specifically
> 
> 
> @JsonTypeInfo(use=Id.CLASS, include=As.PROPERTY, property="fqcn", 
> visible=false)
> public abstract class FortEntity
> 
> 
> now requires an id field to be added to all fortress entities when 
> serializing / de-serializing. Can someone provide insight into what problem 
> this is solving?
> 
> 
> ~Chris P.

signature.asc
Description: Message signed with OpenPGP