You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Alex Harui <ah...@adobe.com.INVALID> on 2018/09/25 07:17:12 UTC
XMLList constructor
Looking at XMLList.as, it seems like it won't handle an input string that is more than one XML node, such as:
<employee>
<name>Christina Coenraets</name>
<phone>555-219-2270</phone>
<email>ccoenraets@fictitious.com</email>
<active>true</active>
</employee>
<employee>
<name>Joanne Wall</name>
<phone>555-219-2012</phone>
<email>jwall@fictitious.com</email>
<active>true</active>
</employee>
Is that intentional or a bug?
Thanks,
-Alex
Re: XMLList constructor
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Syntax like that appeared to compile. The empty one didn't. Maybe the compiler didn't generate the right thing, but I haven't gotten that far yet.
-Alex
On 9/25/18, 3:20 PM, "Harbs" <ha...@gmail.com> wrote:
To be clear, it’s not just empty ones:
The following literal should create a two item XMLList:
var myList:XMLList = <>
<employee>
<name>Christina Coenraets</name>
<phone>555-219-2270</phone>
<email>ccoenraets@fictitious.com</email>
<active>true</active>
</employee>
<employee>
<name>Joanne Wall</name>
<phone>555-219-2012</phone>
<email>jwall@fictitious.com</email>
<active>true</active>
</employee>
</>
Harbs
> On Sep 25, 2018, at 8:09 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> Yeah, the compiler's parser did not seem to understand the empty XMLList literal, which is <></>
>
> For now, I think we'll just ask folks to replace that literal with "new XMLList()"
>
> I'm working on a fix for XMLList.
>
> -Alex
>
> On 9/25/18, 3:28 AM, "Harbs" <ha...@gmail.com> wrote:
>
> Yes. I see it is supposed to be able to be created like that.[1]
>
> Note the literal creation of XMLList using <> and </> too. That will probably require work in the compiler to support.
>
> [1]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwso2.com%2Fproject%2Fmashup%2F0.2%2Fdocs%2Fe4xquickstart.html%23literal&data=02%7C01%7Caharui%40adobe.com%7C990b1cc8c0a74c069d6808d623352765%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636735108532252252&sdata=YiQeaVw554rYy7zNL1rpOfg%2B0Z9WmBS3w1ioCqXFlAk%3D&reserved=0
>
>> On Sep 25, 2018, at 10:51 AM, Harbs <ha...@gmail.com> wrote:
>>
>> I’m not sure I was aware you could create an XMLList from markup like that.
>>
>> I assume you know this is supposed to work.
>>
>> I’m not available this week, but I can try and work on this late next week if you want.
>>
>> Thanks,
>> Harbs
>>
>>> On Sep 25, 2018, at 10:17 AM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>>>
>>> Looking at XMLList.as, it seems like it won't handle an input string that is more than one XML node, such as:
>>>
>>> <employee>
>>> <name>Christina Coenraets</name>
>>> <phone>555-219-2270</phone>
>>> <email>ccoenraets@fictitious.com</email>
>>> <active>true</active>
>>> </employee>
>>> <employee>
>>> <name>Joanne Wall</name>
>>> <phone>555-219-2012</phone>
>>> <email>jwall@fictitious.com</email>
>>> <active>true</active>
>>> </employee>
>>>
>>> Is that intentional or a bug?
>>>
>>> Thanks,
>>> -Alex
>>>
>>
>
>
>
Re: XMLList constructor
Posted by Harbs <ha...@gmail.com>.
To be clear, it’s not just empty ones:
The following literal should create a two item XMLList:
var myList:XMLList = <>
<employee>
<name>Christina Coenraets</name>
<phone>555-219-2270</phone>
<email>ccoenraets@fictitious.com</email>
<active>true</active>
</employee>
<employee>
<name>Joanne Wall</name>
<phone>555-219-2012</phone>
<email>jwall@fictitious.com</email>
<active>true</active>
</employee>
</>
Harbs
> On Sep 25, 2018, at 8:09 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> Yeah, the compiler's parser did not seem to understand the empty XMLList literal, which is <></>
>
> For now, I think we'll just ask folks to replace that literal with "new XMLList()"
>
> I'm working on a fix for XMLList.
>
> -Alex
>
> On 9/25/18, 3:28 AM, "Harbs" <ha...@gmail.com> wrote:
>
> Yes. I see it is supposed to be able to be created like that.[1]
>
> Note the literal creation of XMLList using <> and </> too. That will probably require work in the compiler to support.
>
> [1]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwso2.com%2Fproject%2Fmashup%2F0.2%2Fdocs%2Fe4xquickstart.html%23literal&data=02%7C01%7Caharui%40adobe.com%7C19903f22be6446c4b5d808d622d195e9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636734680903994581&sdata=kLKuoQ0BhuCKF4qYZHPV9krKOHSIF2WnUkbXfvcGHFQ%3D&reserved=0
>
>> On Sep 25, 2018, at 10:51 AM, Harbs <ha...@gmail.com> wrote:
>>
>> I’m not sure I was aware you could create an XMLList from markup like that.
>>
>> I assume you know this is supposed to work.
>>
>> I’m not available this week, but I can try and work on this late next week if you want.
>>
>> Thanks,
>> Harbs
>>
>>> On Sep 25, 2018, at 10:17 AM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>>>
>>> Looking at XMLList.as, it seems like it won't handle an input string that is more than one XML node, such as:
>>>
>>> <employee>
>>> <name>Christina Coenraets</name>
>>> <phone>555-219-2270</phone>
>>> <email>ccoenraets@fictitious.com</email>
>>> <active>true</active>
>>> </employee>
>>> <employee>
>>> <name>Joanne Wall</name>
>>> <phone>555-219-2012</phone>
>>> <email>jwall@fictitious.com</email>
>>> <active>true</active>
>>> </employee>
>>>
>>> Is that intentional or a bug?
>>>
>>> Thanks,
>>> -Alex
>>>
>>
>
>
>
Re: XMLList constructor
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Yeah, the compiler's parser did not seem to understand the empty XMLList literal, which is <></>
For now, I think we'll just ask folks to replace that literal with "new XMLList()"
I'm working on a fix for XMLList.
-Alex
On 9/25/18, 3:28 AM, "Harbs" <ha...@gmail.com> wrote:
Yes. I see it is supposed to be able to be created like that.[1]
Note the literal creation of XMLList using <> and </> too. That will probably require work in the compiler to support.
[1]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwso2.com%2Fproject%2Fmashup%2F0.2%2Fdocs%2Fe4xquickstart.html%23literal&data=02%7C01%7Caharui%40adobe.com%7C19903f22be6446c4b5d808d622d195e9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636734680903994581&sdata=kLKuoQ0BhuCKF4qYZHPV9krKOHSIF2WnUkbXfvcGHFQ%3D&reserved=0
> On Sep 25, 2018, at 10:51 AM, Harbs <ha...@gmail.com> wrote:
>
> I’m not sure I was aware you could create an XMLList from markup like that.
>
> I assume you know this is supposed to work.
>
> I’m not available this week, but I can try and work on this late next week if you want.
>
> Thanks,
> Harbs
>
>> On Sep 25, 2018, at 10:17 AM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>>
>> Looking at XMLList.as, it seems like it won't handle an input string that is more than one XML node, such as:
>>
>> <employee>
>> <name>Christina Coenraets</name>
>> <phone>555-219-2270</phone>
>> <email>ccoenraets@fictitious.com</email>
>> <active>true</active>
>> </employee>
>> <employee>
>> <name>Joanne Wall</name>
>> <phone>555-219-2012</phone>
>> <email>jwall@fictitious.com</email>
>> <active>true</active>
>> </employee>
>>
>> Is that intentional or a bug?
>>
>> Thanks,
>> -Alex
>>
>
Re: XMLList constructor
Posted by Harbs <ha...@gmail.com>.
Yes. I see it is supposed to be able to be created like that.[1]
Note the literal creation of XMLList using <> and </> too. That will probably require work in the compiler to support.
[1]https://wso2.com/project/mashup/0.2/docs/e4xquickstart.html#literal
> On Sep 25, 2018, at 10:51 AM, Harbs <ha...@gmail.com> wrote:
>
> I’m not sure I was aware you could create an XMLList from markup like that.
>
> I assume you know this is supposed to work.
>
> I’m not available this week, but I can try and work on this late next week if you want.
>
> Thanks,
> Harbs
>
>> On Sep 25, 2018, at 10:17 AM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>>
>> Looking at XMLList.as, it seems like it won't handle an input string that is more than one XML node, such as:
>>
>> <employee>
>> <name>Christina Coenraets</name>
>> <phone>555-219-2270</phone>
>> <email>ccoenraets@fictitious.com</email>
>> <active>true</active>
>> </employee>
>> <employee>
>> <name>Joanne Wall</name>
>> <phone>555-219-2012</phone>
>> <email>jwall@fictitious.com</email>
>> <active>true</active>
>> </employee>
>>
>> Is that intentional or a bug?
>>
>> Thanks,
>> -Alex
>>
>
Re: XMLList constructor
Posted by Harbs <ha...@gmail.com>.
I’m not sure I was aware you could create an XMLList from markup like that.
I assume you know this is supposed to work.
I’m not available this week, but I can try and work on this late next week if you want.
Thanks,
Harbs
> On Sep 25, 2018, at 10:17 AM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> Looking at XMLList.as, it seems like it won't handle an input string that is more than one XML node, such as:
>
> <employee>
> <name>Christina Coenraets</name>
> <phone>555-219-2270</phone>
> <email>ccoenraets@fictitious.com</email>
> <active>true</active>
> </employee>
> <employee>
> <name>Joanne Wall</name>
> <phone>555-219-2012</phone>
> <email>jwall@fictitious.com</email>
> <active>true</active>
> </employee>
>
> Is that intentional or a bug?
>
> Thanks,
> -Alex
>