On Wed, 01 Jun 2011 14:33:47 -0300, Lenny Primak <lpri...@hope.nyc.ny.us>
wrote:
My current project is to refresh a client's web site using tapestry. The
web site currently uses JSP. We have a JEE/web service backend that
uses JPA/EJB3.1 which we will continue to use.
We now have a JEE based authorization service API based on plain method
calls now.
What we want is to keep the current login scheme and add LDAP and
possibly Facebook ID and openid.
For using Facebook ID and OpenID, check
http://tynamo.org/tynamo-federatedaccounts+guide. Beyond that, I can't see
why using the existing API in Tapestry would be different from your
existing code, besides that Tapestry templates don't allow code
(scriptlets). I'd suggest you to build some components to encapsulate
common scenarios (something like a IfUserHasPermission component), maybe a
couple mixins, and using the ComponentRequestFilter and/or RequestFilter
pipelines for cross-page logic.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, 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
