I have a server-side JAX-WS SOAPHandler
(on WebSphere v8) that in certain cases needs to respond to the client with a SOAP response that it has in a String variable
I had the same issue after upgrading the WAS FP 8.5.5.10 to 8.5.5.12. We had two Services with exactly same method name but different targetNameSpace,like DomainService1 has 'get' method and DomainService2 also has 'get' method, but WAS 8.5.5.12 throws this exception and doesn't give any clue to find the root cause. Apparently WAS is more strict in recent version with the naming of the methods.
This was the exception: org.apache.axis2.jaxws.wrapper.impl.JAXBWrapperException: An internal assertion error occurred. The com.xxx.web.myapp.services.jaxws.GetResponse JAXB object does not have a xxxxxStatus xml
After changing the name of the method specific to each service 'getABC' and 'getPQR' it worked!!!
hope this works!