Issue 54: Ignore missing elements/attributes and control whether to set the fields to null or leave them out
Status:  Verified
Owner:
Closed:  Sep 2011
Project Member Reported by alex.id....@gmail.com, Sep 22, 2011
I'm working on a project where objects retrieve varying pieces of data 
from different calls, each one setting more properties on the object. 
The problem is that FlexXB seems to treat missing elements and 
attributes as null and sets the object properties as such. That means 
subsequent calls which retrieve data for an object that has already 
been serialised and is kept in a cache provider gets its properties 
nulled by any fields that are missing in the new call. 
Is this the intended functionality? If so, if might be nice to check 
for missing elements and attributes and then not set the value as 
null, or at least add another field in the parsley tag that either 
turns this on, or off if you changed the default behaviour. I realise 
that some backend xml serializers simply ommit null fields, but some 
way to control this would be nice.


Sep 22, 2011
Project Member #1 alex.id....@gmail.com
(No comment was entered for this change.)
Status: Fixed
Labels: -Type-Defect Type-Enhancement
Apr 14, 2012
Project Member #2 alex.id....@gmail.com
(No comment was entered for this change.)
Status: Verified