SmartGwt 3.0
I have a client side integration using the RestDataSource where integer (and other) fields might be null in the response xml.
I've worked around it by just not including null fields in the response xml.
I've tried just using the empty string ("") to have the server send: <fieldName></fieldName>.
When this gets to the client side NOT_NULL criterion is no longer valid.
(Which is stated in the OperatorId doc: value is non-null. Note empty string ("") is non-null )
So my question is what does the client expect in the xml response that would cause it to create a field with null as it's value?
I have a client side integration using the RestDataSource where integer (and other) fields might be null in the response xml.
I've worked around it by just not including null fields in the response xml.
I've tried just using the empty string ("") to have the server send: <fieldName></fieldName>.
When this gets to the client side NOT_NULL criterion is no longer valid.
(Which is stated in the OperatorId doc: value is non-null. Note empty string ("") is non-null )
So my question is what does the client expect in the xml response that would cause it to create a field with null as it's value?
Comment