Parsing JSON doesn't seem to work - tracing the same does! (why?)
I have an activity with a Java step to parse JSON:
try {
myStepPage.adoptJSONObject(myStepPage.getString(".property"));
} catch (InvalidStreamError ise) {
oLog.error("Invalid Stream Error parsing JSON: ", ise);
}
And it seems to work... somewhat, but doesn't always set the actual resulting properties on the page;
but if I trace the same activity, it always works and always fully populates the page -- what's the difference?
Accepted Solution
Unitedhealth Group, Inc.
US
UPDATE: I found out it isn't the JSON parsing that is having trouble -- I was setting the property (the source string) from a utility function using "pg.putString(propName, sValue);" but it turns out that unless I called getXML on the page immediately thereafter, that property value wasn't actually set, and thus no JSON to parse...
Instead, if I specifically use "pg.getValue(propName).setValue(sValue);" then it works.
Unitedhealth Group, Inc.
US
So, I also learned that if I invoke getXML on the page (I added "oLog.infoForced(pg.getXML());" for debugging), then the page updates, as well -- so the question is: what does getXML do and what does Tracing do that both force the page to update, but w/o that, the properties appear to be missing ?
Accepted Solution
Unitedhealth Group, Inc.
US
UPDATE: I found out it isn't the JSON parsing that is having trouble -- I was setting the property (the source string) from a utility function using "pg.putString(propName, sValue);" but it turns out that unless I called getXML on the page immediately thereafter, that property value wasn't actually set, and thus no JSON to parse...
Instead, if I specifically use "pg.getValue(propName).setValue(sValue);" then it works.