<soapenv:Body>
<soapenv:Fault xmlns:axis2ns4="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>axis2ns4:Client</faultcode>
<faultstring>The endpoint reference (EPR) for the Operation not found is http://localhost:9082/sampleAppWeb/managecustomerlink and the WSA Action = . If this EPR was previously reachable, please contact the server administrator.</faultstring>
<detail/>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
The above is the SOAP response that seemed mindbogglingly complex but just as simple to resolve. There's not much information in Google about it except generic answers like
Service might not be up, check the service! Port might be wrong. But I had everything right.
Hello! This is an Axis2 Web Service!
I saw this coming at my end point. So what's the issue here?
The issue is that in the XSDs there is multiple reference. Not that it's not legal, but for some reason the endpoint was unreachable.
My input XSD was having 2 references to 2 different XSDs. First one being the header, second one being another XSD with values. Such a reference was causing this issue and once I removed that reference and had my elements and attributes in the First xsd itself, the issue was gone and the request was hitting the code.
It's very important to revisit the schema and the XSDs even though the references are legal between two XSDs there might be a drawback in how the request reaches the code through the schema
It's very important to revisit the schema and the XSDs even though the references are legal between two XSDs there might be a drawback in how the request reaches the code through the schema
Will post screenshots soon.
No comments:
Post a Comment