VMware {code} Community
ankurbhargava
Contributor
Contributor

Missing action extensions on vSphere upgrade

Hi,

Our Flex based UI plugin module has action extension points both on Actions menu (+ right click on object) AND under Manage view. These have filtering criterion so they appear only for certian object types. It works well until someone upgraedes their vSphere Web server to 6.0 u2 or newer. I don't see any errors and didn't find any docuemtation on what has changed... closest I saw was Action menu's are now flattened to top level. Appreciate suggestsions. Am including the plugin file snippet for reference. 

Thanks.

0 Kudos
3 Replies
ankurbhargava
Contributor
Contributor

For easier reference - 

   <!-- Manage view / Virtual Machine Level -->

   <extension id="com.my.plugin.views.manage.MyManageView.manageViews">

      <extendedPoint>vsphere.core.vm.manageViews</extendedPoint>

      <object>

         <name>#{my.label}</name>

         <componentClass className="com.my.plugin.views.manage.MyManageView"/>

      </object>

   </extension>

 

  <!-- Adding actions on Virtual Machine -->

   <extension id="com.my.plugin.vm.protect.action">

      <extendedPoint>vise.actions.sets</extendedPoint>

      <object>

         <actions>

             <!-- Adding protect action on Virtual Machine -->

            <com.vmware.actionsfw.ActionSpec>

            <uid>com.my.plugin.vm.actions.protect</uid>

               <label>#{applyProtection.label}</label>

               <acceptsMultipleTargets>false</acceptsMultipleTargets>

               <command className="com.my.plugin.views.actions.MyVMProtectActionCommand"/>

            </com.vmware.actionsfw.ActionSpec>          

          </actions>

      </object>

      <metadata>

        <!-- This filters the action to be visible only on VMs -->

        <objectType>VirtualMachine</objectType>

        <propertyConditions>

            <com.vmware.data.query.CompositeConstraint>

                <nestedConstraints>

                    <com.vmware.data.query.PropertyConstraint>

                        <propertyName>isvmprotected</propertyName>

                        <comparator>EQUALS</comparator>

                        <comparableValue>

                            <Boolean>false</Boolean>

                        </comparableValue>

                    </com.vmware.data.query.PropertyConstraint>

                </nestedConstraints>

               </com.vmware.data.query.CompositeConstraint>

        </propertyConditions>        

      </metadata>

   </extension>

0 Kudos
ankurbhargava
Contributor
Contributor

Any suggestions folks ? Other than the plugin.xml file definitions are there other integration points that I need to be looking into ? 
0 Kudos
stoevm
VMware Employee
VMware Employee

Hi ankurbhargava,

First of all sorry for the delayed answer.

1) In <resources> <resource lofcale="{locale}" ...

     change 'lofcale' to 'locale'.

2) I don't know if you sent me the whole plugin.xml, but in order to use the actions you need to place them somewhere

     for example use vsphere.core.menus.solutionMenus extension point, to add the actions you defined to a VM object(I guessed that you are using actions only on VM's) ,

     or you can use vmware.prioritization.listActions to add an action in the list view of a specific object.

Cheers,

--Martin

0 Kudos