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" <[email protected]> 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 <[email protected]> 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 <[email protected]> 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>[email protected]</email> >> <active>true</active> >> </employee> >> <employee> >> <name>Joanne Wall</name> >> <phone>555-219-2012</phone> >> <email>[email protected]</email> >> <active>true</active> >> </employee> >> >> Is that intentional or a bug? >> >> Thanks, >> -Alex >> >
