Unsupported or unrecognized policy causes smart policy selection to fail
Last updated on MAY 24, 2017
Applies to:Oracle Weblogic Server - Version 10.3.5 and later
Information in this document applies to any platform.
A JAX-WS webservice client that uses a WSDL that contains an unsupported/unrecognized policy (WS-Addressing policy, in this case), causes the Smart Policy selection to always choose the default policy, which is the first of the options. So the symptom of the issue is that the client always attempts to secure the request using the first policy in a multiple policy situation, no matter what is set for the smart policy selection process.
See the following doc on policies with multiple alternatives and the smart policy selection process:
The smart policy selection process fails when there is an unrecognized/unsupported policy. In this instance, the policy is WS-Addressing. This is explicitly unsupported; however, its presence in the client-read WSDL causes Smart Selection to always choose the default (first policy in the policy options).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms