JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write.
Hi developers!
How do you debug implementation code in .impl classes of REST.API in InterSystems IRIS?
Especially if you don't have access to globals, so no things like:
Set ^AAA="here we are"not possible in this case.
Suppose I have the following signature of the REST.API method called as POST and containing JSON. :
I would like to know which are the best practices of using Streams in Interoperability messages.
I have always use %Stream.GlobalCharacter properties to hold a JSON, or a base64 document, when creating messages. This is fine and I can see the content in Visual Trace without doing anything, so I can check what is happening and resolve issues if I have, or reprocess messages if something went wrong, because I have the content.
But I think this is not the best way of using Streams.
Hi devs!
What is the best way to return JSON in IRIS for a GET request in a REST app?
This is how I do it now:
ClassMethodAs%Stream.ObjectThe query is used vs the following persistent class:
%PersistentAsWhat I don't like:
1. "Unnecessary" "manual" writes of "[]":
2. Code block repeat for the first segment to excuse "," :
3. I should introduce an "artificial" PersonId to make the response include record ID's (thanks to @Robert Cemper):
%IntegerYour ideas?
There's been quite a bit of discussion lately in this forum on the tools available in IRIS for using both XML and JSON, and debate on cross-conversion between the two formats.
A week or so ago I posted details of a set of tutorials I'd put together on integrating the Node.js-based QEWD technology with IRIS, working over a network. As part of that set of tutorials, I've been detailing how to use the various multi-model capabilities of the build-in QEWD-JSdb abstraction of IRIS.
I was trying the %JSON.Adapter backport to cache and try it also in IRIS and i found a kind of an issue regarding to export and object to json that is an inheritance of %ListOfObjects
If we have a list of elementtype of and object and then we try to export this to a json we get this json instead of a correct json.
exported json:
{
"ElementType":"test.element",
"Size":"1"
}
Json that we want:
[
{
"field1":"testField1",
"field2":"testField2"
}
]
Test classes:
Class test.elementList Extends
Class test.Main Extends %RegisteredObject
{
ClassMethod Run()
{
Set elem = ##class(test.