Return-Path: Delivered-To: apmail-incubator-geronimo-dev-archive@incubator.apache.org Received: (qmail 11699 invoked by uid 500); 8 Aug 2003 07:16:30 -0000 Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: geronimo-dev@incubator.apache.org Delivered-To: mailing list geronimo-dev@incubator.apache.org Received: (qmail 11684 invoked from network); 8 Aug 2003 07:16:29 -0000 Received: from p5085664f.dip0.t-ipconnect.de (HELO dhcppc3.smilebase.org) (80.133.102.79) by daedalus.apache.org with SMTP; 8 Aug 2003 07:16:29 -0000 Received: from dhcppc3.smilebase.org (localhost.smilebase.org [127.0.0.1]) by dhcppc3.smilebase.org (8.12.8p1/8.12.8) with ESMTP id h787GxBd000779 for ; Fri, 8 Aug 2003 09:16:59 +0200 (CEST) (envelope-from chris@dhcppc3.smilebase.org) Received: (from chris@localhost) by dhcppc3.smilebase.org (8.12.8p1/8.12.8/Submit) id h787Gxe5000778 for geronimo-dev@incubator.apache.org; Fri, 8 Aug 2003 09:16:59 +0200 (CEST) Date: Fri, 8 Aug 2003 09:16:59 +0200 From: Christian Trutz To: geronimo-dev@incubator.apache.org Subject: Re: Project Goals Message-ID: <20030808071659.GD550@dhcppc3.smilebase.org> Mail-Followup-To: Christian Trutz , geronimo-dev@incubator.apache.org References: <20030808065332.87877.qmail@web21501.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20030808065332.87877.qmail@web21501.mail.yahoo.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD dhcppc3.smilebase.org 4.8-RELEASE FreeBSD 4.8-RELEASE X-Location: Europe, Germany, Bonn X-Accept-Language: de en X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Fri, Aug 08, 2003 at 08:53:32AM +0200, Emmanuel Bernard wrote: > Way to do it > ============ > Using Maven as developement process tool 1+ > Full Unit Testing coverage (JUnit) 1+ > > Geronimo is JMX based vs Geronimo has a JMX interface > (?) > Solution proposed: > * JMX core of the modular J2EE stack (initial > contributors approch to stay focused) > * Avalon core of the modular J2EE stack > * HiveMind core of the modular J2EE stack > * Home grown Micro kernel core of the modular J2EE > stack > * EJB central piece of Geronimo ?? i think the best solution is: begin from scratch! i mean ideas (patterns) like IoC (Avalon) should be implemented but the kernel should not depend on other piece of software. I mean the kernel of course use things like Digester and so on but it should not BE another piece of software. i think the problem is: if for exemple Avalon changed, the geronimo kernel changed automaticaly or is a branch of avalon, a avalon-geronimo-branch. I am a fan of Avalon! But i think geronimo should be a alternative to avalon! I think geronimo will be the big brother of avalon, but also a alternative! > > Persistence layer use spec front end (EJB, JDO) > delegating to a runtime chosen persistence manager > coordinating plugins actions (caching, locking, > versioning). Reuse approche for persistence manager > impl : OJB, Hibernate, ... > > Geronimo has one and only one EJB Container, but the > implementationof the EJB container should differ (?) > Issue: relation between Geronimo core and EJB > container. > > Think about classloading strategy, and think again. > > Use Aspect or not (?) > Use Aspect or not for the first geronimo steps (?) > Develop home grown aspect framework or use an existing > one (?) > > Reflexion vs/and (bytecode) generate code discussion > > JNDI impl shared with Tomcat (jakarta commons) (?) > > Docs, docs, docs... especially on architecture vision > > Emmanuel > > ___________________________________________________________ > Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais ! > Yahoo! Mail : http://fr.mail.yahoo.com