Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

Plugin Manager - errors need to be localized

Details

  • Case Links:
    none
  • Regression:
    No
  • Story Points:
    0

Description

All errors need to be localized from the server to the UI

Issue Links

Activity

Hide
Scott Feldstein added a comment -

Here are the proposed errors:

plugin.manager.deploy.super.user:
Only a super user can manager plugins

plugin.manager.delete.filesystem.perms:
Could not remove plugin {0} from {1} or {2}. You may not have write privileges on the file and/or directory or the files may not exist.

plugin.manger.bad.file.extension:
cannot recognize file extension of {0}, will not deploy plugin

plugin.manger.file.xml.wellformed.error:
could not parse xml doc, {0} is not well-formed

plugin.manger.jar.manifest.does.not.exist:
manifest does not exist in {0}, jar file could be corrupt. Will not deploy.

plugin.manger.file.ioexception:
IO Error, could not open {0}

Show
Scott Feldstein added a comment - Here are the proposed errors: plugin.manager.deploy.super.user: Only a super user can manager plugins plugin.manager.delete.filesystem.perms: Could not remove plugin {0} from {1} or {2}. You may not have write privileges on the file and/or directory or the files may not exist. plugin.manger.bad.file.extension: cannot recognize file extension of {0}, will not deploy plugin plugin.manger.file.xml.wellformed.error: could not parse xml doc, {0} is not well-formed plugin.manger.jar.manifest.does.not.exist: manifest does not exist in {0}, jar file could be corrupt. Will not deploy. plugin.manger.file.ioexception: IO Error, could not open {0}
Hide
Annie Chen added a comment -

plugin.manager.deploy.super.user=Only a super user can manager plugins
plugin.manager.delete.filesystem.perms=Could not remove plugin {0} from {1} or {2}. You may not have write privileges on the file and/or directory or the files may not exist.
plugin.manger.bad.file.extension=cannot recognize file extension of {0}, will not deploy plugin
plugin.manger.file.xml.wellformed.error=could not parse xml doc, {0} is not well-formed
plugin.manger.jar.manifest.does.not.exist=manifest does not exist in {0}, jar file could be corrupt. Will not deploy.
plugin.manger.file.ioexception=IO Error, could not open {0}

Show
Annie Chen added a comment - plugin.manager.deploy.super.user=Only a super user can manager plugins plugin.manager.delete.filesystem.perms=Could not remove plugin {0} from {1} or {2}. You may not have write privileges on the file and/or directory or the files may not exist. plugin.manger.bad.file.extension=cannot recognize file extension of {0}, will not deploy plugin plugin.manger.file.xml.wellformed.error=could not parse xml doc, {0} is not well-formed plugin.manger.jar.manifest.does.not.exist=manifest does not exist in {0}, jar file could be corrupt. Will not deploy. plugin.manger.file.ioexception=IO Error, could not open {0}
Hide
Annie Chen added a comment -

You can add whatever uploading plugin error message key to applicationResource.properties and throw PluginDeployException with the message key and parameters(optional). However, it won't work properly if there are more than 4 parameters.

Show
Annie Chen added a comment - You can add whatever uploading plugin error message key to applicationResource.properties and throw PluginDeployException with the message key and parameters(optional). However, it won't work properly if there are more than 4 parameters.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    2 years, 49 weeks, 6 days ago