Hi All,,
I have output like below from my xslt :
http://schemas.xmlsoap.org/soap/envelope/;>
40 car 2019-01-17T00:00:00
37 table 2019-01-17T00:00:00
35 book 2019-01-17T00:00:00 26
box 2019-01-17T00:00:00
which gets converted into below json in postman :
{ "Result": {
On Sunday, 21 January 2018 8:14 PM, vikram nayak
wrote:
Hi All,,
I have output like below from my xslt :
http://schemas.xmlsoap.org/soap/envelope/;>
40 car 2019-01-17T00:00:00
37 table 2019-01-17T00:00:00
35 book 2019-01-17T00:00:00 26
box
Hi thusitha,
On 21 Jan 2018 1:18 pm, "Thusitha Thilina Dayaratne" <
thusithathil...@gmail.com> wrote:
Hi Rukshan,
Does your environment contains anything or is it a just empty map?
Yes it contain the ldap context factory and other connection url and
credentials data.
Thanks
Thusitha
On
Hi Vikram,
This is happening because your XPath generates multiple elements with below
structure, which not your desired output.
**
* 26*
* box*
* 2019-01-17T00:00:00*
* *
In an XML point of view, you are expecting an xml content like below, which
is not a valid XML
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
Hi Ruwan and Jayanga,
The term 'secured' is only related to the 'callSecure()' call right?
And that is only an internal method which should be called from every other
method which needs secured access.
IMO 'Secured' is a valid name if we have a have something like template
method which provides
Hi Rasika,
+1,
I assume in the default configuration we will keep both these values to
false since by default we would not need the publish info to DAS. Also,
when you say publish operation response, does it mean we are publishing all
operation info such as application list, device info and
Hi Rasika,
In a UX point of view, IMHO it's better to have both options as
configurations giving the user more flexibility of using the product.
Furthermore it would avoid sending in unnecessary data if only one option
is needed.
+1 for having separate configurations IMO.
On Mon, Jan 22, 2018
Hi Rasika,
+1 for the change, but how about :
true
true
IMO, this wording makes a bit more sense. Also, let's make sure to include
explanations as to what these params enable.
Thanks and Regards,
Ruwan Yatawara
Technical Lead,
WSO2 Inc.
email : ruw...@wso2.com
mobile : +94 77
Hi Shanika,
When we write test cases we normally keep the configured(already changed)
file somewhere and replace that with the relevant file before running that
particular test. Is it possible for you to do the same with test grid ?
Thanks,
Iqbal
On Mon, Jan 22, 2018 at 12:53 PM, Shanika
+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].
Hi All,
In IoT Server v3.1.0 geo location services is enabled with the following
configuration;
true
true
With the new feature developments; In latest IoT Server(master branch);
now we also allow publishing device-info responses through the same
configuration.
true
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
Hi Rasika & all,
BTW, with our current implementation we are publishing operation response
of DeviceInfo if *PublishOperationResponse* is enabled. So shall we changed
it as *PublishDeviceInfoResponse* ? Also since it is useful to publish
Operation response payloads to Analytics for further
Hi Shanika,
Do you use any configuration automation tools such as puppet, Ansible, etc
? If that is not the case, how do you update the configuration files such
as carbon.xml, api-manager.xml?
You can add site.json to puppet or any configuration automation tool.
Another option is to maintain
Have you tried something like this [1]? You need to add another XSLT
processing after you get the original output.
[1] -
https://stackoverflow.com/questions/1571083/how-to-remove-root-element-from-xml-file
Regards,
Gihan
On Mon, Jan 22, 2018 at 8:12 AM, Vinod Kavinda wrote:
>
Hi Lahiru,
Changes have been committed.
Thanks,
On Mon, Jan 22, 2018 at 9:55 AM, Malaka Gangananda wrote:
> Hi Lahiru,
>
> I will do the needful.
>
> Thanks,
>
> On Mon, Jan 22, 2018 at 9:51 AM, Lahiru Madushanka
> wrote:
>
>> Hi all,
>>
>> This issue
Hi Malaka,
Thanks
On Mon, Jan 22, 2018 at 10:06 AM, Malaka Gangananda
wrote:
> Hi Lahiru,
>
> Changes have been committed.
>
> Thanks,
>
> On Mon, Jan 22, 2018 at 9:55 AM, Malaka Gangananda
> wrote:
>
>> Hi Lahiru,
>>
>> I will do the needful.
>>
>>
Hi Lahiru,
I will do the needful.
Thanks,
On Mon, Jan 22, 2018 at 9:51 AM, Lahiru Madushanka
wrote:
> Hi all,
>
> This issue is fixed now.
>
> I am attaching the diff of the fix below.
>
> Could someone please add this to the SVN
>
> Thanks,
> Lahiru
>
--
Malaka.
--
Hi all,
This issue is fixed now.
I am attaching the diff of the fix below.
Could someone please add this to the SVN
Thanks,
Lahiru
Index:
modules/core/src/main/java/org/apache/synapse/config/SynapseConfigUtils.java
===
---
On Mon, Jan 22, 2018 at 1:12 PM, Irham Iqbal wrote:
> Hi Shanika,
>
> When we write test cases we normally keep the configured(already changed)
> file somewhere and replace that with the relevant file before running that
> particular test. Is it possible for you to do the same
21 matches
Mail list logo