On Feb 12, 2008, at 12:49 PM, Joe Bohn wrote:
Kevan Miller wrote:
Server assembly -- We could look at simplifying this process. You
currently must have application plugins in order to include
application capabilities in a server assembly. Why not export
based on one or more installed applications? Also, in addition to
our current, low-level module/plugin focus, can we have a simpler/
higher-level focus? Some users would rather choose "JMS" rather
than "org.apache.geronimo.configs/activemq-ra/2.1/car", "JSP/
Servlet", "Deploy" capabilities, etc.
Yes, I think this "template" notion (I think we've used that term
at other times) is the next logical step in the flexible server.
I'm not sure if you were thinking only in terms of the Server
Assembly function (from the console or command line) ... but this
would make a lot of sense from a remote install capability as
well. We could get to a point where the user could just download
the framework assembly and then choose to install a template from a
"Template Repository" for something like "Tomcat minimal" or "Jetty
full Java EE 5" and have the server image upgraded to that
configuration.
that's basically how the server assemblies are made today, the
template being the pom. I think the only missing bit is extracting
the schemas. This could be done through a "copy-resource" function
in a plugin xml.
thanks
david jencks
Joe
