[kepler-dev] [Bug 4978] New: Create additional 'module' property for any menu entries that are inserted by non-core modules

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4978

           Summary: Create additional 'module' property for any menu
                    entries that are inserted by non-core modules
           Product: Kepler
           Version: 1.x dev
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: interface
        AssignedTo: berkley at nceas.ucsb.edu
        ReportedBy: swriddle at gmail.com
         QAContact: kepler-dev at kepler-project.org


As of revision r24221 and r24222-3 on the branch, there's a way to avoid those
errors that look like:

      [run] ERROR (org.kepler.gui.MenuMapper:getActionFor:271) Exception trying
to create an Action for classname: <org.kepler.tagging.TagManagerAction>:
      [run] null (java.lang.ClassNotFoundException:
org.kepler.tagging.TagManagerAction)

Those come from modules inserting menu entry information into the persistent
gui module configuration and then the user removing that module from their
active configuration. The system still tries to create that entry, which
references a class that is no longer available. If a property named 'module' is
created as a peer to 'name' and 'value', then the menu entry will only be
generated if a module by that name is in the active configuration. See
org.kepler.module.tagging.Initialize from the tagging module for an example of
how to do this without hardwiring the module name.

So in order to eliminate error messages like the above, these additional
properties need to be created when the menu entry is added to the gui
configuration.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.