

You should not specify this attribute in the client Web Service because it is possible that the runtime retrieval of the WSDL file might not succeed. The JWS file that implements the client Web Service that invokes the reliable Web Service ( ReliableClientImpl.java) incorrectly includes the wsdlLocation attribute of the annotation.Pay particular attention to the namespaces and assertion order.

To workaround this problem, update the example WS-Policy file (called ReliableHelloWorldPolicy.xml) to look like the default reliable messaging WS-Policy file included in WebLogic Server, described in Use of WS-Policy Files for Web Service Reliable Messaging Configuration. In particular, the WS-Policy file includes an incorrect wsrm namespace and lists the assertions in an incorrect order. The example uses an incorrect WS-Policy file.
