HI,
using SOAPUI to import WSDL into an existing service failed with the following error.
Caused by: java.io.IOException: HTTP 403 Forbidden: http://aud722003s.perpetual.com.au:53305/ino:dav/ino:dav/redist/jaxr
HI,
using SOAPUI to import WSDL into an existing service failed with the following error.
Caused by: java.io.IOException: HTTP 403 Forbidden: http://aud722003s.perpetual.com.au:53305/ino:dav/ino:dav/redist/jaxr
Found the problem. The locationCentraSite element must be WebDAV location and it must cover “/CentraSite/CentraSite”. You can actually traverse the valid WebDAV path to find
http://localhost:53305/CentraSite/CentraSite/ino:dav/ino:dav/redist/jaxr
The response from SOPAUI
uddi:f26d691b-7c71-11e0-a5f3-dcc8731da3a3
bad news guys.
The modified WSDL did not get updated… (modified=false). I check the WSDL via “download document” or WSDL link… not changed
selected items…[com.centrasite.control.registry.items.ServiceItem@5a2d40bf [name=myMulplyInt2] [key=uddi:f26d691b-7c71-11e0-a5f3-dcc8731da3a3;modified=false]]
selected obj…com.centrasite.control.registry.items.ServiceItem@5a2d40bf [name=myMulplyInt2] [key=uddi:f26d691b-7c71-11e0-a5f3-dcc8731da3a3;modified=false]
I think this is it…
The original attachment of WSDL was done via HTTP (refer to error before). So we need to be consistent with how we attach the WSDL
Try ImportWsdlService webservice again with importWSDLviaHTTP operation – works!! – so we must be consistent with how we attach the WSDL.
Request:
http://localhost:53305/CentraSite/CentraSite/
http://devw034.perpetual.com.au:5555/ws/UDDI_IN:myMulplyInt2?WSDLl
Org1
service
Response:
uddi:f26d691b-7c71-11e0-a5f3-dcc8731da3a3
Try CentraSite Contro and attach modified WSDL via URL also works.
I will try to the FILE method soon with both CentraSite and web service - importWsdlService.importWSDLwithAttachment operation.
Sorry guys… I am very new to this. ImportWsdlService will create a new service with WSDL attached if the service does not exist. Otherwise, it will update the service with the modified WSDL. I tried with the importWSDLviaHTTP only. I will try the importWSDLviaAttachments soon.