I appreciate your valuable feedback! Currently, a user doesn't have that much choices, as we only allow the user to assemble a new server out of plugins in local server, unless we want to change this behavior.
So if a user installs the geronimo-tomcat-javaee5 assembly, he can only choose tomcat + axis2. If a user installs the geronimo-jetty-javaee5 assembly, he can only choose jetty + cxf. To simplify things, here is what I suggest. We allow the users to choose from - __ Web __ JMS __ Web Services __ EJB __ OpenJPA __ Deployment __ Admin Console __ Cluster (tomcat only?) Then the user can just select one or more functions they need and request for the customer assembly server to be created. Optionally, the user can add on additional deployed apps or other system modules then request for the customer assembly server to be created. Lin On Tue, Aug 12, 2008 at 4:10 PM, David Jencks <[EMAIL PROTECTED]> wrote: > > client profiles might be apropriate too. > > I wonder how much of this is actually necessary? e.g. if you install the > jetty-deployer plugin you get jetty too. If you install the jetty-console > you get jetty.... > > What if we had a "select the parts" page that was organized differently than > the list of plugins.... e.g. checkboxes for web, ejb, webservices. If you > say yes to web, you get to choose jetty/tomcat, whether you want deployment, > whether you want the console. > > Choosing web or ejb gives you the opportunity to include openjpa ( or maybe > toplink in the future) > Choosing webservices gives you the choice of cxf or axis2 > > > Just some more or less random thoughts > david jencks >
