Before DevelopmentArticleIn the example of Jax-ws handler in, when I need to establish a corresponding WebService client, Com. sun. XML. internal. WS. streaming. xmlstreamreaderexception: Unexpected xml tag. error
I found a lot of problems with the Jax-ws version, but I am not doing this.
In fact, the problem lies in the implementation of handler. When I implement the soaphandler interface, I use eclipse to automatically generate functions defined by excuses, among which
@ Override <br/> Public Boolean handlemessage (soapmessagecontext context) {<br/> // todo auto-generated method stub <br/> return false ;//!!! <Br/>}
The value "false" is returned when automatic generation is generated, which means that the current WebService will be terminated after the handler, that is, the WebService will not return a normal result, this also causes the tag recognition error when the client wants to return the SOAP message from parse. So it will be normal if it is set to true. This function will be called twice, one is WebService inbound and the other is outbound.