Options: 1. Change the schema and specify that the "id" attribute must be namespace qualified, e.g., <x:attribute name="id" type="x:string" form="qualified"/> 2. Change the schema and specify a different name for the attribute 3. Turn off multi-refs 4. Use literal rather than SOAP encoding
Anne On 8/18/06, xu cai <[EMAIL PROTECTED]> wrote:
I got a weird issue. In my case, the soap response generated by axis engine is not a valid xml, because there are two "id" attribute in multiRef element. see the snippet : <multiRef id="id4" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/ soap/encoding/" id="mgw_monitoring_enabled" xsi:type="ns4:ReplyColumn" xmlns:ns4="http://www.foo .com/" xmlns:soapenc=" http://schemas.xmlsoap.org/soap/encoding/";>Y</multiRef> the first "id" attribute is the id of the element, it's referenced by other element. as you know, the soap response generated by axis always looks so, there are so many "mutiRef" element. ... the second "id" attribute is the caused by my wsdl file , it means the "id" of this record, it's the content of the reply data. WSDL interface is finalized, I also think the "id" attribute make sense and should be changed. So my question is, is there any way to fix this porblem. allow customer add a attribute "id" to their expected reply data ? Since "id" attribute is used by "multiRef", can we define "id" attribute in wsdl ? .... many thanks -- - xucai
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
