This content has been marked as final. Show 5 replies
The reason the change lists are empty is because there just aren't that many changes to the Flex 2 framework at this time.
If you look at the Flex 3 SDK download page ( http://labs.adobe.com/technologies/flex/sdk/flex3sdk.html), you'll see that new builds are posted pretty much daily, and the change lists provide *literally* hours of entertainment.
Thanks, Peter, but that could not possibly be true. Or at least not that true. For instance, I was told that a particularly egregious webservice bug was fixed in build 185039. The most recent Flex 2 sdk milestone build is 185962, which should include the fix I care about. However, the changelist doesn't contain anything of substance, and this build is dated two full months after the most recent release (aka Hotfix 3). I wouldn't want to risk using it without knowing what else happened during those two months.
Does this sound like the bug in question?
Build 185179, Fri Oct 19 2007
Change: Thu Oct 18 2007 11:24:56 (svetlink)Revised creation of array values in XMLDecoder.
Simplified encoding of xsi:nil and tweaked encoding of element wildcards in XMLEncoder.
QA: not yet. just cleaning up before verifying fixes.
Doc: not yet
No, it is that XML tokens in Strings that are passed to Webservice calls are no longer escaped after Hotfix 2. You can see my report and the reply that it had already been fixed at https://bugs.adobe.com/jira/browse/SDK-13378.
OK, I checked with Eng/QA team for that feature and it seems that the fix was made in the Flex 3 source code only, and not in the Flex 201 source.