Hi Martin, I would advice against option 2 because you lose an easy update path to newer versions of the security module.
Tell us more about your use-case so we can see what the options are. Cheers, Jeroen On Wed, Nov 19, 2014 at 2:24 PM, Martin Balmaceda < [email protected]> wrote: > Hola > > I see there are two options to working with the security addon: > > 1. "Out of the box" = add maven dependency and change shiro.ini > 2. Base your project on the security addon example application > > I would like to know if there is a way to use my own ApplicationUser domain > object to extend the users while still using for option 1. > > I would use option 2 but it seems the example application is using a > simplified or perhaps older version of wicket (I could be mistaken on this > though). > > Please let me know if this does makes sense. > > Regards > Martin > > -- > to do is to be. dobedobedo >
