| Issue 57: | XmlArray member cannot have different namespace to parent/alias | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Hi alex.
XmlArray members now inherit the namespace from the XmlArray namespace (or the XmlClass if available).
In some cases members require an alternate namespace from the parent:
e.g.
<data>
<a:Categories>
<b:item>1<b:/item>
<b:item>1<b:/item>
</a:Categories>
</data>
I've implemented a patch against trunk that adds an optional memberNamespace property to XmlArray to allow for these scenarios. Includes serialize/deserialize tests
BTW - these recent patches are all related to supporting the out-of-the-box xml structure for .NET WPF services.
What version of the product are you using? On what operating system?
flex 2.3.0, trunk
Please provide any additional information below.
Sep 30, 2011
#1
domdelor...@gmail.com
Sep 30, 2011
Well, this can be achieved by setting that namespace on teh item class itself. Have you tried that?
Sep 30, 2011
Yeah - except when dealing with simple types like string or int. I should have mentioned that in the description. In .net WPF XML serialization simple/primitive types are namespaced in this way.
Sep 30, 2011
oh, I see now
Status:
Accepted
Labels: Milestone-2.3.1
Apr 14, 2012
(No comment was entered for this change.)
Status:
Fixed
|