Return-Path: Delivered-To: apmail-avalon-dev-archive@www.apache.org Received: (qmail 91202 invoked from network); 21 Oct 2003 10:49:44 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 21 Oct 2003 10:49:44 -0000 Received: (qmail 24735 invoked by uid 500); 21 Oct 2003 10:49:42 -0000 Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 24484 invoked by uid 500); 21 Oct 2003 10:49:40 -0000 Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list dev@avalon.apache.org Received: (qmail 61543 invoked from network); 21 Oct 2003 08:30:52 -0000 Reply-To: From: "Eric Pugh" To: "'Turbine Developers List'" , "'Avalon Developers List'" Subject: RE: [RT] My Merlin Wish List Date: Tue, 21 Oct 2003 10:31:01 +0200 Message-ID: <006b01c397ad$a961a130$0100a8c0@IQUITOS> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <3F939746.1050900@apache.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi all, I started looking at what Stephen did with the crypto service, and it is very interesting. The Turbine dev team knows we need to come up with something better then ECM, however we just haven't gotton around to writing either a good FortressComponentService or MerlinComponentService. However, if someone has something that they could contribute, that would go a long way towards getting the ball moving on getting the various services in the Fulcrum project moved towards Merlin. Before Turbine 2.4 release, which is focusing on integrating all the services moved to Fulcrum, we need to basically pick our container to run with.. We don't want to go with Fortresss/ECM, and then in 2.5 start swapping to Merlin which could require config changes, so it is definitly on the list to get the MerlinComponentService written. Eric Pugh > -----Original Message----- > From: Stephen McConnell [mailto:mcconnell@apache.org] > Sent: Monday, October 20, 2003 10:05 AM > To: Avalon Developers List > Cc: turbine-dev@jakarta.apache.org > Subject: Re: [RT] My Merlin Wish List > > > > [reposting with correct turbine-dev address] > > > J Aaron Farr wrote: > > >>>Embeddable Merlin containers > >>> servlets > >>> > >>> > >>you mean tomcat/jerry running as a merlin service OR merlin > running as a > >>tomcat/jetty war? ;) > >> > >> > > > >Both of course! :) > > > >Actually, there's a couple things that would be cool here: > > - Tomcat/Jetty running as merlin service > > - An Avalon light weight servlet container (which adds avalon > >lifecycle support to servlets) > > - Easy way to access Avalon services from within service, > action, etc. > >(this can be done via AltRMI or JNDI, but we need to put > together docs > >and examples) > > > >I'm not very familiar with Turbine, but it would be nice to > see Turbine > >services running in Fortress and Merlin without too much trouble. > > > > Hi Aaron: > > Confession - I'm not familiar with Turbine either. > > I have played around with Turbine Fulcrum a bit - did some > treaking of the > crypto package and things are working fine (using crypto > component). I've > got a local copy running against Merlin 3.2 using the new test case as > part of own my own test-and-validation-release-suite. > > I'm interested in the Avalon/Turbine connection because I > would like to > play with the potential of Turbine as a smart web-service > system that we > plugin on the container facilites side of merlin. I'm also a > interested > in potential applications of Turbine on the server side (just > a hunch). > > Cheers, Steve. > > -- > > Stephen J. McConnell > mailto:mcconnell@apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: turbine-dev-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org