Release Notes › SOA Security Manager Release Notes › Known Issues › General Issues › Operation-Level Policy Changes Not Committed In Certain Situation When Configuring Application Policy From WSDL (69006)

Previous Topic: "JVM - JNI code: -1(JNI_ERR)" Errors in Policy Server Log (68569)

Next Topic: Clicking Back Button in Secure Web Services from WSDL Wizard Sometimes Causes "Array Index out of range error -1" (72176)
Operation-Level Policy Changes Not Committed In Certain Situation When Configuring Application Policy From WSDL (69006)

When creating an application policy from a WSDL file, operation-level policy changes in the Define Web Service Protection Policy table are lost if you return to the top level by clicking the All Web Services link and then immediately click the Next button to proceed.

Workaround

After you have specified operation-level policy changes for a particular port, if you click the All Web Services to return to the top level of the Define Web Service Protection Policy table, click any other button or link (for example, the link for that port again) before clicking Next to ensure the operation-level changes are committed.