Yes, the expert/showall option should be added to the other Create Plugin pathways for create/export.

-Donald


Ellen Tang wrote:
Hi,

Thanks for replying.

Do you mean that we can put a "expert" or "show all" option in the "Create Plugin" portlet? Because I can see the "Expert User" checkbox when I click the "Assemble a server" button and choose which plugins or plugin groups to include in the server assembly, but I can't see any option like that in the "Create Plugin" portlet or when I click the "Export Plugin" button.

Ellen

2009/11/13 Donald Woods <[email protected] <mailto:[email protected]>>

    Yep, a "expert" or "show all" option would be the safest, where the
    default would be not to show any org.apache.geronimo configs.


    -Donald


    Joe Bohn wrote:


        We do something similar to this with the "expert mode" in the
        various application views where we disable actions like stop,
        restart, and uninstall on system modules unless the user
        specifies that they are an "expert user" via the check-box.

        To make the determination in those cases we look at the prefix
        for the component id to see if it is
        "org.apache.geronimo.configs".  However, it seems this is no
        longer sufficient as our prefixes have been changing to include
        o.a.g.plugins and o.a.g.framework while this feature has not
        been updated.  Perhaps we should change this function to only
        check for "org.apache.geronimo".

        Joe

        Ivan wrote:

            It may sound a good idea, but the question is that how we
            could distinguish the system modules and applications
            deployed by users ?

            2009/11/13 Ellen Tang <[email protected]
            <mailto:[email protected]> <mailto:[email protected]
            <mailto:[email protected]>>>

               Hi,

               I'm currently reviewing the contents on the UI of the
            "Plugins"
               portlet in G 2.2 admin console. I have a question for the
            "Create
               Plugin" function.

               As we can see, currently the drop-down list in the
            "Create Plugin"
               portlet shows all the CAR files on the server, including
            system
               plugins that already exist in the
            "%GERONIMO_HOME%\repository\"
               folder. For example, you can find the plugin
"org.apache.geronimo.configs/activemq-broker/2.2-SNAPSHOT/car"
            in
               the directory
"%GERONIMO_HOME%\repository\org\apache\geronimo\configs\activemq-broker\2.2-SNAPSHOT",

               which contains the "geronimo-plugin.xml" file already.
            However,
               according to the "Help" contents of the "Create Plugin"
            portlet, the
               function of this portlet is that "The console will
            generate the
               geronimo-plugin.xml file that stores the plugin metadata
            information
               for your project and package it into a car file."

               My question is that do we really need to include the
            system plugins
               in the drop-down list of the "Create Plugin" portlet? If
            the system
               plugins already exist in the
            "%GERONIMO_HOME%\repository\" folder
               and they already have the "geronimo-plugin.xml" file, the
            users
               would not need to use this "Create Plugin" portlet to
            create these
               plugins again. Besides, this portlet doesn't do anything
            else to the
               system plugins apart from exporting them as files, which
            the users
               already have in the repository. Therefore, I think it's more
               practical to only show the applications and/or
            application plugins
               in the drop-down list of this portlet.

               Does anyone think that it's a good idea to leave out the
            system
               plugins but only keep the application plugins in this
            portlet? Maybe
               we can do that in the 3.0 release?

               Any comments are welcome.

               Thanks!

               Ellen





-- Ivan




Reply via email to