Hi,
I have a solution menu defined in my project's plugin.xml. I have a nested composite constraint with 2 boolean checks that currently works fine when filtering the menu items:
<extension id="com.me.vm.actions.menu">
<extendedPoint>vsphere.core.menus.solutionMenus</extendedPoint>
<object>
...
</object>
<metadata>
<objectType>VirtualMachine</objectType>
<propertyConditions>
<com.vmware.data.query.CompositeConstraint>
<nestedConstraints>
<com.vmware.data.query.PropertyConstraint>
<propertyName>propertyA</propertyName>
<comparator>EQUALS</comparator>
<comparableValue>
<Boolean>true</Boolean>
</comparableValue>
</com.vmware.data.query.PropertyConstraint>
<com.vmware.data.query.PropertyConstraint>
<propertyName>propertyB</propertyName>
<comparator>EQUALS</comparator>
<comparableValue>
<Boolean>false</Boolean>
</comparableValue>
</com.vmware.data.query.PropertyConstraint>
</propertyConditions>
</metadata>
</extension>
If I add a third property constraint, this time numeric, to the composite constraint then the following happens:
1. The solution menu label is not displayed and instead the plugin name is used instead (i.e. all my-ui actions)
2. All actions are visible and enabled regardless of the constraint propery values
3. Under my solutions menu a "More Uncategorized Actions" submenu is added even though there is no hierarchy in my defined extension point.
Do you have any pointers on why this behavior might be seen? Thanks
Example numeric property constraint:
<com.vmware.data.query.PropertyConstraint>
<propertyName>myVersion</propertyName>
<comparator>EQUALS</comparator>
<comparableValue>
<Number>800</Number>
</comparableValue>
</com.vmware.data.query.PropertyConstraint>
