Return-Path: Delivered-To: apmail-incubator-directory-dev-archive@www.apache.org Received: (qmail 16112 invoked from network); 2 Jul 2004 14:56:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 2 Jul 2004 14:56:13 -0000 Received: (qmail 98397 invoked by uid 500); 2 Jul 2004 14:54:45 -0000 Delivered-To: apmail-incubator-directory-dev-archive@incubator.apache.org Received: (qmail 98283 invoked by uid 500); 2 Jul 2004 14:54:44 -0000 Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Directory Developers List" Reply-To: "Apache Directory Developers List" Delivered-To: mailing list directory-dev@incubator.apache.org Received: (qmail 98190 invoked by uid 99); 2 Jul 2004 14:54:43 -0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=FROM_ENDS_IN_NUMS,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received: from [205.152.59.66] (HELO imf18aec.mail.bellsouth.net) (205.152.59.66) by apache.org (qpsmtpd/0.27.1) with ESMTP; Fri, 02 Jul 2004 07:54:42 -0700 Received: from [172.16.1.8] ([68.218.232.170]) by imf18aec.mail.bellsouth.net (InterMail vM.5.01.06.08 201-253-122-130-108-20031117) with ESMTP id <20040702145427.PXAS1776.imf18aec.mail.bellsouth.net@[172.16.1.8]> for ; Fri, 2 Jul 2004 10:54:27 -0400 Subject: [eve] merlin wrappers From: Alex Karasulu To: directory Content-Type: text/plain Message-Id: <1088780218.16055.7.camel@fermi.trunk.joshua-tree.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 02 Jul 2004 10:56:58 -0400 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Steve, Quick question for ya. I just finished the consolidation of the Eve interfaces and pojo services into a single maven project. This has the SPI interfaces for all the components and the default service implementation as a POJO only (non-Avalon specific component). I moved all the merlin wrapper projects into their own area. Do you think its worth it to keep the Merlin wrappers for each component separate? The reason why I ask this is because of thoughts that came my way while consolidating. First Merlin probably will have the ability at some point to hot swap blocks because of the attention to detail with respect to class loading schemes. We can still benefit from this to allow hot swaping if the Avalon wrapper components are in separate jars. Is this a correct assumption? The second thought was what the heck am I going to do with the different conf/ directories I have for integration tests on the Merlin wrappers using Merlin-Unit. Right now having each component in its own project makes it easy to have its separate conf/ directory to test the component with. The top level compoent for the frontend called the 'frontend component' will have the final block.xml for the server's configuration. What are your opinions and thoughts here? Alex