Skip to Content
0
Mar 05, 2008 at 03:16 PM

NET -> XI -> WAS Scenario: elementFormDefault="qualified" SUPPORTED???

174 Views

Hello Gurus,

I've been looking and looking and have found nothing:(

I have the following scenario:

.NET <-> XI <-> WAS

In the XI I have created the XSDs-> Messages -> Interfaces and then generated WSDL and Proxies in the WAS. In the XSDs no attribute 'elementFormDefault' was set, means per default elementFormDefault="ungualified".

I generated the XML Messages and tested it with JMeter or other Tool, just to make sure the XI -> WAS works.

Than I gave the WSDLs to .NET guys. They changed the elementFormDefault to "qualified" in order to create client proxy classes correctly(so they say). Then they called XI Services and boom, nothing worked. The messages they generate are different that these we generated, because of this attribute elementFormDefault set to "qualified".

My general question is, is it supported at all, this attribute elementFormDefault="qualified"??

I tried later to upload an XSD file to XI with this attribute set, but the Editor said, that this is erroneus and would not accept it. So for me this is not supported, but I have found a document, an excel file

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2089f29b-b10a-2a10-5297-e258df0c1bfc

and it says, that Editor is not supported, but Java and ABAP Proxies are supported. Are these client or server proxies? Because for me it's not consistent, to say editor does not support it and proxies do.

I would appreciate every help and hints.

Maybe there is some way for .NET to work it around, or maybe for XI to tell the WSDLs and generated proxies to use qualified.

Systems that we use:

.NET: MS .NET Framework v3.0 und + Windows Communication Framework (WCF)

XI: Netweaver 04 640 SP18

WAS: SAP NetWeaver 2004s Rel 7.0 SP10

best regards

Simon