Adding Pawel who is looking into this issue. From: Lioy, Marcello [mailto:ml...@qce.qualcomm.com] Sent: Tuesday, November 22, 2016 3:52 PM To: Vincent Du <v...@affinegy.com>; Arvind Padole <arvi...@exchange.microsoft.com> Cc: Josh Spain <jsp...@affinegy.com>; allseen-c...@lists.allseenalliance.org Subject: RE: [Alljoyn-core] Remaining Blocker (ASACORE-3486)
Sorry everyone for the confustion. Are we sure the issue isn’t one with conversion to the XML string? Arvind – who worked on the XML APIs? Including Kevin and Dan in case they have some insight. Bug is: https://jira.allseenalliance.org/browse/ASACORE-3486 From: Vincent Du [mailto:v...@affinegy.com] Sent: Tuesday, November 22, 2016 3:07 PM To: Lioy, Marcello <ml...@qce.qualcomm.com<mailto:ml...@qce.qualcomm.com>> Cc: Josh Spain <jsp...@affinegy.com<mailto:jsp...@affinegy.com>>; allseen-c...@lists.allseenalliance.org<mailto:allseen-c...@lists.allseenalliance.org>; Arvind Padole <arvi...@exchange.microsoft.com<mailto:arvi...@exchange.microsoft.com>> Subject: Re: [Alljoyn-core] Remaining Blocker (ASACORE-3486) Marcello: Sorry for the confusion. The issue I was referring to is a separate one from ASACORE-3486, but it happens to be XML-related as well. It is not blocking because it is more of a XML tag and functions naming issue that would confuse API users. Thanks, Vincent On Tue, Nov 22, 2016 at 4:26 PM, Lioy, Marcello <ml...@qce.qualcomm.com<mailto:ml...@qce.qualcomm.com>> wrote: I thought I saw that Vincent iddn’t think it was a blocker (I haven’t read the whole thread though). Have we made it through the other Sec2.0 testing? From: Josh Spain [mailto:jsp...@affinegy.com<mailto:jsp...@affinegy.com>] Sent: Tuesday, November 22, 2016 2:09 PM To: allseen-c...@lists.allseenalliance.org<mailto:allseen-c...@lists.allseenalliance.org> Cc: Lioy, Marcello <ml...@qce.qualcomm.com<mailto:ml...@qce.qualcomm.com>>; Arvind Padole <arvi...@exchange.microsoft.com<mailto:arvi...@exchange.microsoft.com>>; Hertel, Carrie <carrie.her...@oregonstate.edu<mailto:carrie.her...@oregonstate.edu>>; Pawel Winogrodzki <pawe...@microsoft.com<mailto:pawe...@microsoft.com>> Subject: Remaining Blocker (ASACORE-3486) All, We have one remaining potential blocker, ASACORE-3486<https://jira.allseenalliance.org/browse/ASACORE-3486>. This is an issue with XML validation of Security 2.0 manifest XML. The only workaround is to not use the XML versions of the Security 2.0 functions. @Pawel, can you provide more details on the severity of this bug and whether or not you think it should block the release? Thanks, Josh [Image removed by sender.] Josh Spain Director of Engineering Affinegy, Inc. t.512-535-1700 x1006<tel:512-535-1700%20x1006> a. 1705 S Capital of Texas Hwy, Suite 310, Austin, TX 78746 USA Website<http://affinegy.com> Email<mailto:jsp...@affinegy.com> [Image removed by sender.]<http://www.linkedin.com/in/joshspain> [Image removed by sender.] <http://twitter.com/affinegy> [Image removed by sender.]Latest Tweet:<https://twitter.com/Affinegy> Building the buzz for their IPO ...This is Snapchat’s new Spectacles store in New York City https://t.co/AG1u809qRL via @techcrunch<https://twitter.com/techcrunch> Read More<https://twitter.com/Affinegy/statuses/801009583619735552> [Image removed by sender.]<https://twitter.com/Affinegy> _______________________________________________ Alljoyn-core mailing list Alljoyn-core@lists.alljoyn.org<mailto:Alljoyn-core@lists.alljoyn.org> https://lists.alljoyn.org/mailman/listinfo/alljoyn-core
_______________________________________________ Alljoyn-core mailing list Alljoyn-core@lists.alljoyn.org https://lists.alljoyn.org/mailman/listinfo/alljoyn-core
