Hi,
our QA found a new problem which deals in the changing of the plug-ins custom alarms.
During the plug-in installation we define a number of custom events and alarms. The alarms are not activated. When the customer decides to edit one of these alarms, an error occurs.
It can be reproduced as follows:
1) Have a custom alarm defined (during installation)
2) In the HTML Client (6.7) - select a vcenter in the navigation tree. Navigate to Configure-> Alarm definitions
3) Select the custom alarm , and click on Edit.. Continue through the wizard - nothing needs to be changed to reproduce this.
4) Save the definition.
The following error occurs:
Cannot construct instance of "com.vmware.vise.util.serialization.mixin.TypeNameImplMixin$TypeNameImplBuilder",
problem: null
at [Source: (String) " {
"_type": "com.vmware.vim.binding.vim.alarm.AlarmInfo",
"name": "Acme Test Alarm",
"key": "",
"description" : "this is a test alarm",
"entity" : {
"type" : "Folder",
"value" : "group-d1",
"serverGuid": "aa98acd4-8b59-489b-a5c4-b335690a303a",
"_type" : "com.vmware.vim.binding.vmodl.ManagedObjectReference"
},
"enabled" : true,
"expression" : {
"_type" : "com.vmware.vim.binding.vim.alarm.OrAlarmEx.......
}
So it seems that that the "key" value of the alarm gets lost somewhere - this is similar to the problems we encountered when editing custom roles (earlier discussion).
Could this be confirmed?
Cathy