[ 
https://issues.apache.org/jira/browse/FELIX-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112559#comment-16112559
 ] 

David Bosschaert commented on FELIX-5666:
-----------------------------------------

Hi [~dleangen], just trying to start understanding the problem. 

The first test I started looking at is:
  
JsonBackingObjectSerializationTest.testComplexMapSerializationFirstUsingConversion()

This test creates a DTO: MyDTOishObject and then converts it to a Map. This 
conversion seems to work correctly, but then the conversion from that map to 
the JSON seems to go wrong. Is this a correct assumption? It looks like the 
serialization of a DTO to JSON doesn't work... 

Actually I guess the problem can already be observed by calling 
{{JsonSerializerImpl().serialize(obj).toString()}} directly on the DTO, as the 
result there also contains the {{toString}} key in the JSON.


> Serializer goes into infinite loop
> ----------------------------------
>
>                 Key: FELIX-5666
>                 URL: https://issues.apache.org/jira/browse/FELIX-5666
>             Project: Felix
>          Issue Type: Bug
>          Components: Converter
>            Reporter: David Leangen
>            Assignee: David Bosschaert
>
> I'm only guessing as to what the problem is, following some stepping through 
> the code. I could not find any similar existing test cases, but if the 
> following does not immediately click for [~bosschaert], I will try to add one.
> It appears that, when serializing an object to a "DTO-Type" object to a Map, 
> some kind of backing object is created.
> If the backing object contains a field that instantiates the same DTO, then 
> the loop gets created.
> Example:
> {code}
> public class MyDtoType {
>   public String id;
>   public MyDtoType( String anID ) {
>     id = anID;
>   }
>   public static MyDtoType error() {
>     return new MyDtoType( "ERROR" );
>   }
> }
> {code}
> It looks like the serializer keeps calling the error() method infinitely, but 
> I am not able to easily pinpoint where this happens.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to