Resolution:
Environment
------------
All

Reason
-------
There is a difference in the definition of 'SQL_RETURN' and 'SQL_BATCHRETURN' in older and newer versions of adb.

When a new project is created in adb5.5 this issue is not seen, even after changing the transport from RV to JMS or vice-versa.

1) For the older versions of ADB ,the output of the null field &ltitem xsi:type = "ae:binary.1"&gtAA==</item> , indicates that this item is a binary type data  and its value is empty. The parameter AA== is actually a base64 encoded string.This string needs to be decoded using the xpath formula base64-to-string to get the actual value
2) For ADB 5.5, the explicitNullAttribute is set so as to identify “null” from “empty”


Workaround
-----------
Import a project from a .dat created with new adapter version and letting it overwrite the schemas under adbmetadata.

Why does the adapter publish blank fields in the database as binary "AA=="?