xServer 2.x and SAP issues due to derived classes

This space is dedicated to SAP users - administrators and programmers who want to integrate the xServers. Topics which require specific SAP based knowhow or which deal with SAP based mechanisms will be collected here.

xServer 2.x and SAP issues due to derived classes

Postby Bernd Welter » Tue Oct 16, 2018 3:09 pm

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 ;-)
Bernd Welter
Senior Technical Consultant Developer Components
PTV GROUP - Germany

Bernd at Youtube
User avatar
Bernd Welter
Site Admin
 
Posts: 1412
Joined: Mon Apr 14, 2014 10:28 am

Return to PTV xServer meets SAP