Is not this against the design pattern we discussed ? It was finalized in refactoring discussions with Mark and Mario and I had kept you informed on that. In case it breaks existing consumer we could have let it go in current iteration and implemented this in correct way in major release.

Hi Swati

This is regarding the refactoring issue you ran into before going to leaves.
We should create a new class Person ( having all the extra fields ) and make Member a field of it.
Lets discuss this once you are back.

Regards
Manish