From continuum-dev-return-3469-apmail-maven-continuum-dev-archive=maven.apache.org@maven.apache.org Fri Dec 02 23:51:17 2005 Return-Path: Delivered-To: apmail-maven-continuum-dev-archive@www.apache.org Received: (qmail 96948 invoked from network); 2 Dec 2005 23:51:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Dec 2005 23:51:15 -0000 Received: (qmail 20759 invoked by uid 500); 2 Dec 2005 23:50:25 -0000 Delivered-To: apmail-maven-continuum-dev-archive@maven.apache.org Received: (qmail 18235 invoked by uid 500); 2 Dec 2005 23:50:00 -0000 Mailing-List: contact continuum-dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-dev@maven.apache.org Delivered-To: mailing list continuum-dev@maven.apache.org Received: (qmail 16901 invoked by uid 99); 2 Dec 2005 23:49:44 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Dec 2005 15:49:43 -0800 X-ASF-Spam-Status: No, hits=1.6 required=10.0 tests=MAILTO_TO_SPAM_ADDR,RCVD_IN_BL_SPAMCOP_NET X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [62.193.206.151] (HELO mailsender.amenworld.com) (62.193.206.151) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Dec 2005 09:15:25 -0800 Received: from webmail9.amenworld.com (webmail9.amenworld.com [62.193.206.9]) by mailsender.amenworld.com (Postfix) with SMTP id 00E399D5831 for ; Fri, 2 Dec 2005 18:13:35 +0100 (CET) Received: (qmail 29230 invoked from network); 2 Dec 2005 17:13:42 -0000 Received: from 21.29.99-84.rev.gaoland.net (HELO ?127.0.0.1?) (84.99.29.21) by 0 with SMTP; 2 Dec 2005 17:13:42 -0000 Message-ID: <439080B5.7010901@venisse.net> Date: Fri, 02 Dec 2005 18:13:25 +0100 From: Emmanuel Venisse User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: fr, en MIME-Version: 1.0 To: continuum-dev@maven.apache.org Subject: Re: Design - Replacing Continuum's Web Framework References: <438FC39D.4040708@yahoo.com> <1a5b6c410512012117x144b86b5l76029980c3f07197@mail.gmail.com> In-Reply-To: <1a5b6c410512012117x144b86b5l76029980c3f07197@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Carlos, do you have a simple sample that use acegi? Emmanuel Carlos Sanchez a écrit : > Acegi is based in servlet filters for the protection of urls, so the > web framework used won't impact its use. > Are you planning protecting just urls or any other stuff? acegi can do > authorization and authentication at class, method and instance level > too, but I think that's only needed in a few types of applications. > > I was in a project using JSF and seems that it's adoption is getting > speed, with different implementations and a lot of extensions, > utilities and tools. I've heard very good things about using > Facelets+JSF to create components, and also about Spring MVC, but > seems to me that people using Spring MVC is moving to JSF. > > My 2 cents > > > On 12/1/05, John Casey wrote: > >>Hi everyone, >> >>We've been talking about this for quite awhile in various channels, and >>I wanted to take a few minutes and formalize the discussion. I'll >>capture the highlights of this discussion in the wiki afterwards. I'll >>start by posting my own thoughts, and let you all respond. >> >>Up to this point, Continuum has been built on a web framework called >>Summit, which is part of the Plexus project, and using Velocity as the >>page rendering technology. Summit is still a very young project, and as >>a result has its problems. Given the proliferation of web frameworks out >>there, it seems natural to wonder whether we couldn't find something >>more mainstream and mature that will fit our needs. >> >>The key goal here is to make the web tier as easy to understand as >>possible by the widest possible audience, without sacrificing anything >>in the way of quality. To that end, criteria might include: >> >>* tool support >>* maturity in the form of multiple final releases (or at least one) >>* good integration with JSP (it's the most widely-used rendering >> technology out there for java) >>* ready availability of good documentation >>* integration with a decent security library (think acegi) >>* others? >> >>Another big concern is that we need to be able to make this web >>framework integrate with Plexus without too much funny business. I don't >>expect that to be a big problem, but worth mentioning. >> >>I know that a certain amount of work has been done by Trygve and >>Emmanuel to get WebWork running inside Plexus. Is this the best >>framework? A quick check of Amazon showed three books, only one of which >>is completely concerned with WW. SpringMVC might be another option, >>since it has probably the most natural integration with Acegi. There is >>a certain amount of overlap between Spring and Plexus that we'd probably >>have to map with a custom Spring container or something, but that's >>likely to be everywhere, since dependency injection is such a hot topic >>(and very useful). >> >>What do you all think? >> >>-john >> > > > >