Em Thu, 31 Dec 2009 08:44:00 -0200, Alessandro Bottoni
<alexbott...@gmail.com> escreveu:
1) A quite basic module, or even a well-documented demo, that just takes
into account the most common requirements and uses a set of sensible
defaults. This basic "package" should not have to be extensible or
flexible.
A demo with this features would be a very good idea.
2) An enterprise-level module, like Spring Security. This solution
should have to be flexible and extendible. It should be able to deal
with LDAP, OpenID, JASIG CAS and other providers. It would be used for
complex, enterprise-level apps.
Re-implement something like Spring Security is not feasible, IMHO. It
would need people who know a lot about security, and Tapestry is a Web
framework. In addition, that's an awful lot of code to write and, AFAIK,
very few projects use these security providers (besides OpenID). We should
focus on what will be useful for the most people.
I don't think using Spring Security the Tapestry security module because
it forces the use of Spring. I still need to take a look at
JSecurity/Apache Shiro, but I guess it would fill this need better.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
