geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dillon (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-2328) Why GBeans - reinventing the wheel?
Date Thu, 14 Jun 2007 17:25:25 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason Dillon closed GERONIMO-2328.
----------------------------------

    Resolution: Invalid
      Assignee: Jason Dillon

Um, well one day we will probably change this, but for now... gbeans are here for a while.

> Why GBeans - reinventing the wheel?
> -----------------------------------
>
>                 Key: GERONIMO-2328
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2328
>             Project: Geronimo
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>    Affects Versions: Wish List
>            Reporter: Oleg Gusakov
>            Assignee: Jason Dillon
>
> Guys - why spend time reinventing the wheen with GBean container? One of the key values
of Geronimo was stated as "bring the best of open technologies together rather than rewriting
them". And one of the most fundamental features - initialization/configuration container -
writing it from scratch and making all errors once again?
> Containers have been around since early days of civilization - pico and nano containers,
JBoss'es MBeans, microcontainer, Spring to name a few 
> And the father of them all - plexus: has been around for a decade - simple, reliable,
proven. Why not just take plexus and spend efforts on something really new and exiting?
> You use Maven for the build, so you already have some kind of exposure to it. Throw in
classwords - and Geronimo rules! No headaches from half cooked products. And not deviating
from the stated principles :)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message