So, I think it is not necessary to limit that " 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."
We can list all the function here, and user also can choose them all, If the plugin does not stay in current server, then before the assembling process, a page show a list of the missing plugins and tell that it will download them from the repo on internet to complete the assembly, and also will provide an estimated cost of time for user. Make sense? Rex. 2008/8/13 Jack <[EMAIL PROTECTED]> > Thanks Lin for bringing this up! This is a very valuable improvement to > make the custom server assembly feature truly usable. > > I really like the idea of grouping functions and describing them in a > language that is understandable to users. I think we can organize them in a > hierachy, similar to the way how we select features to install during a > desktop application installation. Grabbed a random snapshot here: > http://www.tenouk.com/clabworksheet/windowspsdk_files/windowssdkpsdk008.png > > As to the proposed list, I would suggest the following changes/additions > * Break down Web further into JSP+Servlet and JSF > * Change OpenJPA to JPA. I guess user does not have to care about whether > it's OpenJPA or whatever else. > * Add JTA, JavaMail. Suppose Security is by default included... > > Last but not least, if a user uses the custom server assembly function in a > customized server (say, without JPA), will we allow the user to select JPA? > > - Jack > >
