Gson should limit the allowed recursion depth about gson HOT 10 CLOSED

Original comment by inder123 on 8 Jul 2008 at 5:44

from gson.

This bug is similar to issue 19 which is fixed in r118, r117, and r116. 
However, I
will leave it open for now to see if we need to provide explicit option to set
recursion depth. One problem is how does anyone know what a good value for the 
depth is? 

Original comment by inder123 on 19 Jul 2008 at 1:09

• Added labels: Priority-Low
• Removed labels: Priority-Medium

from gson.

Original comment by inder123 on 1 Oct 2009 at 3:59

• Added labels: Milestone-Release1.5

from gson.

[deleted comment]

from gson.

I agree to add param dept, It does not work fine when I use Hibernate

Original comment by [email protected] on 22 Dec 2009 at 8:04

from gson.

Original comment by inder123 on 1 Nov 2010 at 10:28

• Removed labels: Milestone-Release1.5

from gson.

Original comment by inder123 on 3 Nov 2010 at 12:25

• Added labels: Milestone-Undefined

from gson.

Why is this needed?

Original comment by [email protected] on 19 Apr 2011 at 6:54

from gson.

I say that recursion should not be used for parsing at all, queues should be 
used instead to avoid code recursion all together.

Original comment by [email protected] on 17 Dec 2011 at 2:25

from gson.

We don't recurse in the streaming parser.

Original comment by limpbizkit on 23 Dec 2011 at 5:35

• Changed state: WontFix

from gson.