I came across to read this post. Where can I find the example that uses tapestry 5 and shiro?
Thanks, Kalle Korhonen wrote: > > On Tue, Feb 17, 2009 at 9:37 PM, Les Hazlewood > <[email protected]>wrote: > >> Basically I'm polling your interest of accommodating internal change >>> requests. If you are already gearing up towards stable 1.0 release you >>> might >>> not be interested or not have time for it, but if you welcome >>> improvement >>> suggestions on internals of the framework, I'd be happy to work with >>> you. >> >> >> We would absolutely appreciate your feedback and contributions - I think >> we're very much open to suggestions prior to 1.0, since it makes sense >> (at >> least to me) to get these kinds of additions in place before a 1.0 stable >> release. >> > > Excellent, it sounds like I'm stepping in at the right time. > > >> The best way is to discuss your ideas and approaches on the dev list >> which >> will then probably lead to Jira issues and patches. With enough due >> diligence and open discussion, there is a very good possibility to become >> a >> committer - we're definitely open to others joining the project as >> committers assuming said due diligence. Just be aware that the ASF >> requires >> signing contributor agreements before that can happen ( >> http://www.apache.org/licenses/#clas). >> So, we definitely look forward to discussion and your ideas. Let loose >> :) >> > > Thanks for the encouraging reply Les. Yes, I'm subscribed to the dev list, > but I didn't want to post there out of the blue all-knowingly, proposing > changes to code that for the intended purpose does work. It's just that > framework programming *is* difficult because it's impossible to know all > the > use cases before people take your code and start using it in a way you > never > even thought of... we've all been there - on both sides of the fence I'm > sure. I don't have a problem being a user for the time being - there's the > burden of a committer, suddenly you are actually responsible for > maintaining > the code and there's only a limited amount of time everybody has. However, > becoming a committer in this case would open up interesting possibilities > for me and the good thing is that I'm in a position where I'm allowed to > allocate some of my time for security related issues. I'm very much aware > of > the apache committer process and meritocracy (which makes an interesting > comparison to Codehaus' dictatorship approach), but never been an Apache > committer. Anyway, we don't have to worry about it for now, let me just > annoy you with a flurry of emails to the dev list first ;) > > Kalle > > -- View this message in context: http://n2.nabble.com/jsecurity-integration-with-Tapestry5-tp2342638p3453949.html Sent from the Shiro User mailing list archive at Nabble.com.
