An unset byte-array field returns 'null' now and not an empty byte[]. This fails every time it is tested.
Should we change the code or the test-cases?
I think returning null makes sense, but so does the empty byte. Both indicate 'no data'. Sincer a NODE field returns null if no value is presnted, maybe a BYTE field (byte array is also an object), and in the future a Date field, should do the same?
Then again, maube BYTE behave similar to STRING fields (which, IIRC return an empty string)?
The following things are succeeding now: nodeList = cloud.getList("" + aaNode1.getNumber(), "aa,bb", "aa.bytefield", "", "", "", "", false); nodeList = cloud.getList(null, "aa,bb", null, "", "", "", "", false); nodeList = cloud.getList(null, "aa,bb", "", "", "", "", "", false);
The test-case is not specifying why it should fail.
I don't think it should fail. Some flexibility in accepting parameters (bull or "" both mean 'no data') makes it easier to use the interface.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
