Metro does not support multiple policy alternatives.

When using a wsit-*.xml configuration with multiple policy alternatives, metro
reports "WSP0035: Policy "null" contains more than one policy alternative.
Please reconfigure the service with only one policy alternative." in an exception.

See for more details
[https://metro.dev.java.net/servlets/ReadMsg?list=users&msgNo=3478](https://metro.dev.java.net/servlets/ReadMsg?list=users&msgNo=3478)

Since many WS-* specifications are not yet widely supported, using policy
alternatives allows one to use the appropriate WS-* specifications and to also
provide failbacks for clients that don't support them. For instance, in our Web
Services, we are using thh WS-Reliable Messaging session mechanism. Since many
client stacks (eg. workflow engines) does not support WS-RM, we opted to support
HTTP session as failback for them. Without support for policy alternatives, it
add a lot of complexity to our deployment.
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[current]

Source: [https://github.com/javaee/metro-wsit/issues/830](https://github.com/javaee/metro-wsit/issues/830)
Author: glassfishrobot

Start by reproducing the WSP0035 exception with a wsit-*.xml configuration containing multiple policy alternatives, using the linked discussion for context. Trace where the policy is rejected and identify the relevant Metro implementation and tests; done means alternatives are accepted and the existing single-alternative behavior remains covered.

Written by the indexing model from the issue text.