| Issue 54: | Ignore missing elements/attributes and control whether to set the fields to null or leave them out | |
| 1 person starred this issue and may be notified of changes. | Back to list |
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.
Apr 14, 2012
(No comment was entered for this change.)
Status:
Verified
|
Labels: -Type-Defect Type-Enhancement