xServer 2.x and SAP issues due to derived classes

[Bernd Welter]

Hi SAP players,

as you might know SAP has caused some issues in the hadling of WSDL files, e.g. when it comes to the processing of derived classes. This was an "optional" challenge within xServer1: e.g. Geocoding was possible by default - problems arised when players wanted to

• use parameter types (SearchOption, NamedSearchOption, ...) which have been derived by other classes (SearchOptionBase, ...)
• retrieve specific response objects (Emission, CenEmission...)
• use arrays

As xServer 2 uses a completely generic approach based on an abstract RequestBase class the issues #1 and #2 will occur by design in 100% of xServer2 calls - if this is still an SAP issue. So this is no longer an option

I just

• wanted to draw your attention to that topic as early as possible
• ask you for your feedback: who did try to create xServer 2 client classes through the malicious WSDL importer? WHat are your experiences?

Best regards from Karlsruhe,
Bernd -- non sap consultant