문제

I came across an issue where a customer is able to open a SAP wsdl using net-beans as well as in .Net but not in soap UI.

When i checked the wsdl i found that service as well as binding tags are not defined or no such tags included. wsdl ends with port-type information.

In soap UI i got an error like no content in the file and when i try to open it in eclipse i am able to open it using web explorer window, but service as well binding information fields are empty. I could see ws-policy elements in customers wsdl.

  1. How he might have produced a wsdl without binding and service information ?

  2. What would be the reason he is telling it is working in .Net?

I am not sure about .Net tools.

  1. Is there any web service client tool which can open the operations without endpoint /service information and send request/response ?..

please help thank you for your time.

도움이 되었습니까?

해결책

I only know a bit about the first question, can't help you with the other ones...

You can request two "flavors" of WSDL from a NW/ABAP system. This is related to the fact that the implementation (programming) of the service is usually performed on a different system and by different people than the configuration of the service.

After the service (or rather a service definition) has been implemented, you can get what's called a "design-time WSDL document". This document does not include the endpoint information - it cannot, because that would require technical information about the target system landscape and its configuration that is simply not available yet.

From the service definition, an administrator can create a configuration. This includes the binding information as well as stuff like base URL, security settings, transport layer settings and so on. With this configuration, you can generate a second WSDL document that contains the actual endpoint configuration.

WSDL generation in SOAMANAGER

라이센스 : CC-BY-SA ~와 함께 속성
제휴하지 않습니다 StackOverflow
scroll top