David Jencks wrote:
>
> On Aug 12, 2008, at 2:59 PM, Lin Sun wrote:
>
>> 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.
>
> true... for now :-)
>>
>>
>> To simplify things, here is what I suggest. We allow the users to
>> choose from -
>>
>> __ Web
> __jsp
>>
>> __ JMS
>> __ Web Services
>> __ EJB
>> __ OpenJPA
>> __ Deployment
>> __ Admin Console
>> __ Cluster (tomcat only?)
> __wadi clustering
>>
>>
>> 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.
>
> I wonder if we can think bigger :-)
>
> What if we distributed something with _all_ the cars in it and
> customizable profiles for the servers we ship now? So, you wouldn't
> unpack a particular server, but the server construction kit. You could
> pick a profile and optionally modify it, then spit out the desired
> server. Then you would be able to pick jetty/tomcat and cxf/axis2 and
> however much deployment you wanted.
Couldn't we consider the maven repos as our server construction kit?
Seems that if users want this level of customization (building a server
from pieces instead of from an already working server) then using the
car-maven-plugin to build a server would be the preferred path.
>
> Alternatively maybe the "assemble a server" can show plugins from more
> than just the current server.
>
> thanks
> david jencks
>
>
>
>>
>>
>> Lin
>>
>> On Tue, Aug 12, 2008 at 4:10 PM, David Jencks <david_jencks@yahoo.com>
>> 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
>>>
>
>
|