Hi
On 14/02/13 14:55, James Talbut wrote:
Hi,
I have a base class ("ExtensionArgumentType") which has ~12 different sub
classes derived from it.
The classes themselves are all defined in an XSD and are primarily used in SOAP.
When I try to communicate with the server using WebClient I get something like:
"ExtensionArgument" : [{
"@xsi.type" : "ns2:ParameterValueType",
"ns2.Name" : "ScalarParameter",
"ns2.Value" : "Value1"
}, {
"@xsi.type" : "ns2:ParameterValueType",
"ns2.Name" : "ScalarComboParameter",
"ns2.Value" : "Value2"
}
I don't mind having the "@xsi.type" parameter there, and I'm happy to write
whatever would be useful in it, but:
1. There is no ns1 anywhere in the HTTP request from WebClient, so how do I
know which prefix to use?
2. I don't want to have prefixes on the other elements (Name& Value).
If I tell the client to ignore namespaces it won't write the xsi.type at all.
If I introduce a namespace map and give it an entry from my namespace to
nothing it removes the namespace from Name/Value, but leaves ns2 on the type
name.
If I introduce a namespace map and give it an entry from my namespaec to something
that prefix is used for Name, Value& type.
Is there any way to get what I'm after?
Passing this with JSON is tricky, and the immediate workaround I can
think of is to get the receiving end to map "ns2" to a specific
namespace (with namespace map), but in your case I guess there could be
up to 12 namespaces...
I can think of a workaround where JSONProvider which sends the data is
configured (via transformation properties) to structure the payload such
that it has enough hints for the receiving JSONProvider to convert the
incoming payload (also with transformation properties) for JAXB to map
it correctly
I wonder if should enhance StaxTransformFeature to change prefixes when
needed too...so for every specific subtype you'd be able to use a
dedicated prefix and thus manage the namespace map on the receiving end
better...
Cheers, Sergey
