admin管理员组

文章数量:1122832

When parsing a returned JSON by NotesJSONNavigator / NotesJSONElement classes,
I get the mentioned message for each top-level JSON object printed to the server console:

In my opinion, I'm handling all possible LotusScript JSON "types" (Jsonelem_type_array, Jsonelem_type_object, Jsonelem_type_boolean, Jsonelem_type_empty, Jsonelem_type_number & Jsonelem_type_string) in my code, so I have no idea where this message is coming from.
Also, the agent completes processing without any error (which would get trapped in my errorhandlers), and the JSON is valid.

I've set the NotesHTTPRequest parameter "PreferStrings" to true (which acc. to the documentation is returning "Unicode rather than UTF8 byte array"), in order to be able to easily check the NotesHTTPRequest "ResponseCode" - could that be causing the issue?

When parsing a returned JSON by NotesJSONNavigator / NotesJSONElement classes,
I get the mentioned message for each top-level JSON object printed to the server console:

In my opinion, I'm handling all possible LotusScript JSON "types" (Jsonelem_type_array, Jsonelem_type_object, Jsonelem_type_boolean, Jsonelem_type_empty, Jsonelem_type_number & Jsonelem_type_string) in my code, so I have no idea where this message is coming from.
Also, the agent completes processing without any error (which would get trapped in my errorhandlers), and the JSON is valid.

I've set the NotesHTTPRequest parameter "PreferStrings" to true (which acc. to the documentation is returning "Unicode rather than UTF8 byte array"), in order to be able to easily check the NotesHTTPRequest "ResponseCode" - could that be causing the issue?

Share Improve this question asked yesterday DonMaroDonMaro 929 bronze badges
Add a comment  | 

1 Answer 1

Reset to default 1

Seems that reading the value of a JSON element with value null triggered the message; after handling the "Jsonelem_type_empty" case separately (and not accessing the element's value at all), the message disappeared.

Funny somehow, that the printed message refers to a datatype 0 - in Carl's findings here you can see that this type should have the value 64...

本文标签: