Re: Geronimo in year 2008

[Hernan Cunico]

David Jencks wrote:

On Feb 12, 2008, at 6:47 AM, Hernan Cunico wrote:

Shiva Kumar H R wrote:

On Feb 11, 2008 10:12 PM, David Jencks <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    On Feb 11, 2008, at 3:14 AM, Shiva Kumar H R wrote:

    On Feb 8, 2008 2:09 PM, David Jencks <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>> wrote:

        3a is implemented in 2.1

    Is there an admin console page for this already implemented?

    yes, the bottom of the plugin page.  Also there's a gshell command
    for it

"Assemble a server" option looks too hidden under other features :( . A portlet on it's own would have better grabbed the attention of users towards it. We must at least highlight it now in our documentation.

I think both. This feature is important enough to be on its own, probably under 'Server' and we definitively need to document in deep how it works. That includes explaining the plugin architecture as well.

I'll see if I can get the plugin architecture documentation kicked off this week.

I think we should either change the left-hand menu item to something more inclusive that "plugins" (my current preference) or create a new group in the left hand menu with "add plugins" "edit plugin" and "extract server" (I think this will make the LHM too long).

The LHM is getting pretty long. I wonder if we can do something to shorten it -- perhaps a tree?

collapsible trees would be nice. That way the list will come down to just 6-7 entries so 
we would be able to bring up new "sections" to the top level.

Cheers!
Hernan

thanks
david jencks

Cheers!
Hernan

 --
Thanks,
Shiva
    david jencks

        Despite my liking for xmlbeans and its unique strengths I
        think a very strong argument can be made for moving the
        deployer code to jaxb.

    Interesting!! Let me do some quick learning of jaxb and start a
    separate thread on this.


        thanks
        david jencks

        On Feb 8, 2008, at 12:30 AM, Shiva Kumar H R wrote:

        I can immediately remember 3 prior discussions in reference
        to this:
            i) "[DISCUSS/FEEDBACK] Usability improvements to
        Geronimo" mail from Prasad in Nov'07

http://www.mail-archive.com/dev@geronimo.apache.org/msg53236.html

            ii) "[Discuss] What next?" mail from DJencks in Aug'07

http://www.mail-archive.com/dev@geronimo.apache.org/msg50660.html

            iii) "[DISCUSS] Geronimo 2.1 - what's next?" mail from
        Matt in Jul'07

http://www.mail-archive.com/dev@geronimo.apache.org/msg48173.html

        Alright, here is my wish list - features that I would love to
        see getting into Geronimo in 2008:
        1) Deployment Environment:
            a) Plan Creator wizards (in Admin Console & in Geronimo
        Eclipse Plugin) for geronimo-application.xml and *many* other
        Geronimo deployment plans.
            b) Geronimo specific annotations: To further simplify the
        specification of Geronimo deployment information, right at
        development time.

        2) Geronimo Eclipse Plug-in (GEP):
            a) Model framework for Geronimo deployment plans:
        Currently it is EMF (Eclipse Modeling Framework). With every
        update to Geronimo deployment schema, it's a major pain to
        generate new EMF classes. If however, GEP uses the same model
        framework as that of Geronimo server (XMLBeans), then at
        least this problem would be solved. IIUC JSR-88 DConfigBeans
        would be the ideal model framework for GEP - in that case
        even if the model framework of server changes in future, GEP
        would be unaffected.
            b) Critical bug fixes
            c) Make "Download and Install" option more intuitive
            d) Customize Web Services Wizard:
        The default implementation of WTP's web services wizard
        embeds an Axis engine inside a web-app and then deploys it in
        a web server such as Tomcat. However this isn't the right
        approach for Geronimo as it already has a global web services
        engine deployed. Hence web services wizard's behavior must be
        customized when deploying onto Geronimo.
            e) Better Remote server support
            f) Testsuite Automation
            g) Integrating JavaEE Samples.

        3) Admin Console Tools:
            a) Server Build Tool: For instance, a "button" to push
        that spits out a server with just what is needed for a set of
        apps and nothing else.

http://www.mail-archive.com/dev@geronimo.apache.org/msg54849.html

            b) Cluster Admin Tools: Geronimo has a lot of partial
        clustering solutions. For instance there's WADI, native
        tomcat clustering, a terracotta integration, and many others.
        A cluster admin tool would be of great help in the setting-up
        and fine-tuning of those clustering solutions.

        I am stuck in 1) a) Plan Creator work for the past year or so
        and it is still not complete! So if I alone work on many of
        those features, God alone knows when I will complete them.
        Any takers/collaborators?

        On Feb 7, 2008 8:28 PM, Vamsavardhana Reddy
        <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

            Hello,

            Geronimo had a great year 2007.  I don't need to re-list
            all our achievements listed in Matt's mail from 31st Dec
            2007

(http://www.mail-archive.com/dev@geronimo.apache.org/msg54994.html). Now that 2.1 is also rolling out, I think it is time we

            start discussing what we want to do in Geronimo in year
            2008.  Let us also discuss what we "must" do to make
            Geronimo an application server of choice.  I would like
            all of us to use this mail thread to put forth our
            thoughts (and any action items some of us may have
            already come up with silently) so that the community can
            see what great heights Geronimo will scale in 2008.

            Thank you.

            ++Vamsi




        --         Thanks,
        Shiva

    --     Thanks,
    Shiva