Hi Ryan, I added you to the Project Members, so feel free to commit your examples. Unfortunately, until now I haven't had time to work on it myself
The idea was to let the code mature in http://code.google.com/p/wicket-jsecurity/ and maybe move it to wicket-stuff later on. Maybe we should move it to wicket-stuff already. My main problem with wicket-stuff is/was that it's not always very clear which projects are still alive and maintained and which are practically dead. And at the time, wicket-stuff had some problems with continuous integration, IIRC. Les, what do you think ? We should change the project name to wicket-ki anyway. regards, Maarten On Wed, Mar 25, 2009 at 7:47 AM, nino martinez wael < nino.martinez.w...@gmail.com> wrote: > Yeah I've for one always been very pro for wicketstuff.. It's nice keeping > things in one place.. Plus as you write if we share a somewhat similar > structure it's potentially easier to maintain.. > > 2009/3/24 Ryan McKinley <ryan...@gmail.com> > > > Hi- > > > > I've been looking to integrate a complex security model with wicket -- > > jsecurity seems really good. I tried messing with: > > http://code.google.com/p/wicket-jsecurity/ > > > > This appears to be a starting place, but does not have any running > example. > > > > In an effort to get things running (and learn JSecurity) i took that + > > wicket-auth-roles and tried to make a functioning core + example. I've > got > > something running and would love to share it... > > > > Should I post this to the google code site? > > > > It makes more sense (to me) if we keep it in the wicketstuff repos -- > that > > way we get the benefit of Jeremy's work to make wickettuff-core much > > cleaner. > > > > Thoughts? > > > > Ryan > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > >
