[ https://issues.apache.org/jira/browse/FELIX-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110372#comment-16110372 ]
David Leangen commented on FELIX-5666: -------------------------------------- Just a thought... but if in the end you believe that the current behaviour of the Serializer is correct, then another possible "solution" is to have a Converters.newDTOConverter(). It would make the serializer marginally better: {code} String s = serializer .serialize( obj ) .with(Converters.newDTOConverter()) .toString(); {code} I still think that the behaviour to start with is not right, though. :-) > 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 > > 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)