On Sat, Dec 26, 2009 at 10:52 AM, Alessandro Bottoni <alexbott...@gmail.com> wrote:
> This is a very good example of what is probably missing in Tapestry, at > least from the point of view of a new user. > > Is this technique documented somewhere? > Is this demonstrated by some existing archetype or demo app? > Is this part of any Maven archetype or of any "canonical" way of > developing applications with Tapestry. > Is this approach "advertised" somewhere on the Tapestry web site? [..] > Maybe a Tapestry 5 component/module would be a good general-purpose > solution for this Authentication/Authorization common need. Maybe even a > HowTo or a demo would be enough. At least, they could be a solution for > 80% of the applications (the ones that uses the approach proposed by > ACEGI/Spring Security, BTW). > > Maybe Tapestry does not need the dozens of components that are available > for other frameworks, like Wicket, but it surely need some ready-to-use, > standard solutions for a few very diffused, very standard needs like > authentication and access control. Did you have a look at the ChenilleKit project? >> In other words, jumping over backwards for integrations with >> technologies is often not the best approach. Yes, it would be nice to >> have a checkbox "compatible with Spring Security" but I'd rather talk >> about how easy it is to create your own custom extensions that work >> precisely as you need. [..] > Even better, it would be fantastic to have a Maven archetype switch to > enable the access control subsystem generation. Even better again, this > could/should be supplied by derived works, like Tynamo (and it will, as > long as I know). This would keep T5 as simple as possible while still > supplying the user with a rich feature set. > > Tynamo and AppFuse are extremely important for Tapestry for many reasons > and one of those reasons is "standardization". As a new user, I expect > to find a canonical way to develop Tapestry/Tynamo applications and a > canonical set of tools. This because I do not want, and cannot, spend a > few weeks trying to discover the right tools and the right design > patterns to be used for the task at hand by myself. As a quite typical > new user, I need /guidance/ as well, not just a toolbox. I think you're completely missing the point. Cheers -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
