geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lin Sun" <>
Subject Re: [DISCUSS] enhance the assemble server portlet usability
Date Tue, 19 Aug 2008 20:20:22 GMT
I have been thinking a bit more on how we achieve this.   Here is my
idea and I welcome your input -

So we have a need to allow users to install groups of plugins(function
profile), instead of individual plugins.   Install individual plugins
are nice for standalone apps, but for system modules, I think it would
be better to allow users to install groups of plugins as functional
profiles(unless the user is an expert user).    What we need is to
expose the groups of plugins for certain functions available to our
users and allow them to select the ones of their interest to build the
customer server.

I am proposing in addition to store plugin metadata of each plugin in
the plugin catalog, we could also host installable groups of plugins
information there (or in a separate catalog file).   For example, for
a function such as Web (same as little G) that has been discussed in
above posts, we could have the following plugin metadata -

<geronimo-plugin xmlns=""
    <name>Geronimo Assemblies :: Minimal + Tomcat</name>
    <category>WEB Profile</category>
    <description>A minimal Geronimo server (Little-G) assembly using
the Tomcat web-container.</description>
    <author>Apache Software Foundation</author>
    <license osi-approved="true">The Apache Software License, Version


        <dependency start="false">

        <dependency start="true">

        <dependency start="true">

        <dependency start="true">

When a plugin is a profile, it means it just contains a group of
geronimo plugin dependencies that are installable and can perform
certain functions.  By installing it, it will simply install the
dependency plugins.

Questions -

How do we build this profile type of plugin?   We could build them
manually initially to try things but maybe c-m-p could be used here.
How do we install this profile type of plugin?  I think we could
leverage the pluginInstallerGBean to install it...when profile is
true, we just download the dependencies.
How/Where should we make this file avail?   We could make this file
avail in geronimo-plugins.xml (or another catalog file in repo) and
with our server assembly (one assembly contains the plugin profiles it
have).  When building customer server, when load all the plugins that
are profile and ask users to pick which ones they want.   If we have a
framework that can install geronimo plugins, a user can just download
the framework and pick from our apache repo on which plugin profiles
they want to build their geronimo server.
How are we handle the upgrade scenarios Joe mentioned?   No idea
yet... I think this is a rather complicated scenario.



View raw message