vSphere

 View Only
Expand all | Collapse all

Migrating existing plugin.xml to plugin.json (Local plugin to Remote)

  • 1.  Migrating existing plugin.xml to plugin.json (Local plugin to Remote)

    Posted Aug 03, 2022 05:41 PM

    Hi @_vladi_ ,  

    I hope you are doing good.

    We are migrating the existing plugin.xml to plugin.json (Local plugin to Remote).

    While executing the plugin-manifest-converter,  I am facing the below Null pointer exception.

    "Starting the migration of plugin xml to json format
    java.lang.NullPointerException
    at com.vmware.h5.sdk.plugin.migration.file.ResourceDefinitionManager.getCssClassesMap(ResourceDefinitionManager.java:192)
    at com.vmware.h5.sdk.plugin.migration.factory.impl.DefinitionsModelFactory.setIconDefinitions(DefinitionsModelFactory.java:108)
    at com.vmware.h5.sdk.plugin.migration.factory.impl.DefinitionsModelFactory.createModel(DefinitionsModelFactory.java:39)
    at com.vmware.h5.sdk.plugin.migration.factory.impl.DefinitionsModelFactory.createModel(DefinitionsModelFactory.java:30)
    at com.vmware.h5.sdk.plugin.migration.factory.impl.PluginDataModelFactory.createModel(PluginDataModelFactory.java:33)
    at com.vmware.h5.sdk.plugin.migration.factory.impl.PluginDataModelFactory.createModel(PluginDataModelFactory.java:17)
    at com.vmware.h5.sdk.plugin.migration.parser.impl.PluginConfigParser.buildPluginData(PluginConfigParser.java:123)
    at com.vmware.h5.sdk.plugin.migration.parser.impl.PluginConfigParser.parse(PluginConfigParser.java:70)
    at com.vmware.h5.sdk.plugin.migration.PluginManifestConverter.main(PluginManifestConverter.java:24)"

    This plugin.xml works fine for local plugins but needs to migrate to a remote plugin.

    Can you please suggest or provide any other way to convert?

     

    This is the same plugin.xml which was posted https://communities.vmware.com/t5/vSphere-Client-SDK-Discussions/Add-Action-Link-Button/m-p/1858303#M3811



  • 2.  RE: Migrating existing plugin.xml to plugin.json (Local plugin to Remote)

    Broadcom Employee
    Posted Aug 11, 2022 08:41 AM

    Hi,

     

    The plugin manifest converter tool works well in the general use case, however, it may not work correctly when encountering some plugin specifics. Plugin developers may have really complex plugin structure, or they may have chosen different file structure, file names, file contents etc.

    Even though the tool may be helpful, we recommend developers to write their plugin.json manually after carefully reading the documentation. This will improve their understanding of the plugin.json semantics and usage, and will prevent many problems.

     

    Best Regards,

    Denis