Limitations of ABAP Webservice proxy generator....

[LeonardoAraujo]

I would like to have your opinion on this:

After some testing and research, I've found that the ABAP Webservice Proxy generator has limitations and doesn't work with all WSDLs.

I tried to create a webservice proxy for the following WSDL but it doesn't work.

[http://www.xignite.com/xFutures.asmx?WSDL]

I get the following error:

Proxy generation terminated: WSDL error (<extension> not supported)

The long text says

The language element

"<extension>"

was used in the WSDL document.

Here is the comment made by the provider of the service:

We investigated the issue and it seems that the problem is a limitation with the ABAP 4 proxy generation language. It is unable to support the Extension standard which is a very basic WSDL standard that has been around for many years. All our return classes inherit from a standard class called Common and this inheritance is described using the Extension attribute. Every other SOAP parser out there seem to have no problem with this standard.
Apparently this is known limitation of ABAP 4 as you discovered yourself. 

I would appreciate if someone could comment on or confirm this limitation. Also, if you know of developments on the way to get this addressed, it would be helpful.

Thanks

Leonardo De Araujo

[Former Member]

hi,

the limitation is a fact.

here are [more limitations|http://help.sap.com/saphelp_nw04/helpdata/en/de/705c3c3806af06e10000000a11402f/content.htm], including enumerations which i really miss.

Why? I think SAP's strategy is(was?) not to supply a full fledged soap runtime on the ABAP WAS alone but force you to use PI(XI) to make full use of webservice/SOAP functionality and communicate in kind of a limited fashion with your ABAP backends. I Might well be wrong since I don't know and don't understand their strategy.

anton

[LeonardoAraujo]

Thanks. Your answer reassures my position.

I understand the strategy to "force/push" customers to use PI (XI). The problem I have is with the licensing of PI. Unless it has changed, we need to pay licenses per PI interface (if not SAP to SAP). That completely inviabilize lots of possible interfaces.

I have a business model that I am working on to have companies providing market information to SAP systems via webservices. The problem is that there are lots of webservices already available out there, but few work with the ABAP proxy generator in ABAP (at least with the company I am working with).

Frustrating...

Thanks again.

Leonardo

[Former Member]

Hi Leonardo,

Abap Proxy doesn't support <extension> element in WSDL.

Here is your confirmation

http://help.sap.com/saphelp_nw04/helpdata/en/de/705c3c3806af06e10000000a11402f/content.htm

See the info under XSD limitation.

If you want to know the supported WSDlLand XSD types by ABAP, go through this link.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0abcc5a-1569-2a10-e6b7-8e5d108a...

This PDF document contains doesn't contain any info but it contains a link where you can download the excel.

Hope this confirmation was required. You have to use PI

Regards,

Piyush