Disable Property Expansions

Rao,

Thank you for responding and I will definitely try to show an example.  At a very high level we have implemented a third party product that provides migration functionality that allows us to export policy definitions from one environment to another.  In essence they provide get and post methods that we invoke using SOAP UI.  Within a policy you can create variables that use a ${variableName} parameter.

Here is an example of a section of XML that is produced via a get method sent to the export service using SOAP UI:

        <L7p:ComparisonAssertion>

            <L7p:CaseSensitive booleanValue="false"/>

            <L7p:Expression1 stringValue="${entryPoint}"/>

            <L7p:Expression2 stringValue=""/>

            <L7p:Negate booleanValue="true"/>

            <L7p:Operator operator="EMPTY"/>

            <L7p:Predicates predicates="included">

                <L7p:item binary="included">

                    <L7p:CaseSensitive booleanValue="false"/>

                    <L7p:Negated booleanValue="true"/>

                    <L7p:Operator operator="EMPTY"/>

                    <L7p:RightValue stringValue=""/>

                </L7p:item>

            </L7p:Predicates>

        </L7p:ComparisonAssertion>

We would then use the import service via a put method to migrate the policy definition to a new environment.

If we were then to export the policy definition from the new environment it would look like this:

        <L7p:ComparisonAssertion>

            <L7p:CaseSensitive booleanValue="false"/>

            <L7p:Expression1 stringValue=""/>

            <L7p:Expression2 stringValue=""/>

            <L7p:Negate booleanValue="true"/>

            <L7p:Operator operator="EMPTY"/>

            <L7p:Predicates predicates="included">

                <L7p:item binary="included">

                    <L7p:CaseSensitive booleanValue="false"/>

                    <L7p:Negated booleanValue="true"/>

                    <L7p:Operator operator="EMPTY"/>

                    <L7p:RightValue stringValue=""/>

                </L7p:item>

            </L7p:Predicates>

        </L7p:ComparisonAssertion>

In this example SOAP UI is replacing the variable ${entryPoint} with an empty string.

An example of what a Policy would like from the third party GUI is as follows:

Add Audit Details: “Policy Fragment: aPolicyFragment”

Compare Variable: ${entryPoint} is not empty; If Multivalued all values must pass

Include Policy Fragment: aPolicyFragment2

In the end we do not want SOAP UI to expand the ${entryPoint} variable as that variable is needed within the third party policy.

Does that help explain issue.  Regardless thanks for your help.

Ron