If there are iterations inside Person, that is Person's problem.
If there are such iterations, Person should declare them in its javadoc pages, and tell you how to use them; there has to be a method which does that.
You call whichever method there is, and that should be designed to take care of all iterations. If it doesn't, then Person has been designed incorrectly. In fact having such public fields is bad practice, breaching data encapsulation and hiding. Also having Person objects inside fields of the Person class risks getting into an infinite recursion.
You might be able to get this sort of thing to work
Good luck with it