Error 500 when displaying WSDL

[former_member185995]

Hello SOA experts,

I'd like to ask, if someone was troubled with similar issue as we are now. We have developed Java WS, based on PI - ESR definition. All is done on SAP PI 7.1 SP8.

After deployment from NWDI to Java WAS we generated Service Endpoint in Java SOA MANAGER. The service runs correctly, when tested from WS Navigator.

The problem is that when someone/something (SW) wants to display/download WSDL file. First try of WSDL displaying in web browser ends ok, but when the URL is re-entered, we got following error message:

500 Internal Server Error - SAP NetWeaver Application Server 7.10 / AS Java 7.10 - No Service is found using request url <the path of WebService> - Details: No details available

Moreover - as mentioned, the WS runs from WS Navigator and from PI SOAP Commonucation Channel correctly. But when I need to access it from WebDispatcher, the server returns HTTP code 404. The same result is returned, when web service's URL is entered to web browser.

Can anybody suggest, what might be wrong ?

Thank you

Best regards

Tomas

[former_member185995]

Hello again,

we think we found the problem, but we are not sure, how to solve it. The thing is, that the JavaWebService is developed in NWDI under the development component with connection to CMS track.

It seems, that during generation of Service Endpoint the name of development component is inserted into the path of the service. The development component's name is "core/main/ws1", so the slashes are changed for the symbol

~

in the URL. So at the end, the WSDL URL looks with escaped symbols

~

like this : http://<host>:<port>/sapws/domain.net/core%7Emain%7Ews1ear_domain.net%7Ecore%7Emain%7Ews1_EJB_SIINVO...

And as we are trying to call it - the escaped symbols are the problem. The reason is, that some browseres and e.g. SOAP test tools unescape the URL before opening the HTTP connection. It seems that SAP WebDispatcher does the same. And that's why the JavaWebService is not accessible through WebDispatcher.

Are we correct in this and if so can we work around it somehow ?

Thank you in advance.

Regards

Tomas