Thanks for the valuable responses. This is been fixed in [1].
[1] - https://github.com/wso2/carbon-business-process/pull/497
Regards,
Vinod
On Mon, Jan 22, 2018 at 1:55 PM, Milinda Perera wrote:
> Hi,
>
> Actually, we have created a wrapper to avoid changes done internal
> implementation (such
Hi,
Actually, we have created a wrapper to avoid changes done internal
implementation (such as changes in libraries) in future, not to affect
already existing BPMN processes. That's why we have limited result object
types. otherwise, we can return any object type.
Thanks,
Milinda
On Mon, Jan 22,
Hi,
Do we need to filter the data type here. If result is not a Map or List Can
we return the result as it is?
Thanks,
Waruna
On Mon, Jan 22, 2018 at 12:18 PM, Vinod Kavinda wrote:
> Hi All,
> I'm working on fixing the issue [1]. The reason for the issue is we have
> not considered the *null *i
+1, no exact reason for not considering null, as I remember, most probably
missed it.
On Mon, Jan 22, 2018 at 12:18 PM, Vinod Kavinda wrote:
> Hi All,
> I'm working on fixing the issue [1]. The reason for the issue is we have
> not considered the *null *in the code line [2]. According to the JSO
Hi All,
I'm working on fixing the issue [1]. The reason for the issue is we have
not considered the *null *in the code line [2]. According to the JSON spec
[3], null also treated he same way like other primitive types.
Any particular reason for not to add *null?*
Shall we add the null also in the