Thanks for the feedback, but i already figured out what i did wrong. Can somebody get me a brown bag, because i forgot to call super.init() in the init method of the webapplication class
Ted 2008/2/22, richardwilko <[EMAIL PROTECTED]>: > > > A few questions: > > 1) does your session extend AuthenticatedWebSession > 2) if so what does your getRoles() method in your web session look like > 3) presumably you mean @AuthorizeInstantiation(Roles.USER) - without the > stars? > 4) do you manually set any of the options on getSecuritySettings() in your > webapplication class (afaik you shouldn't, i don't) > > Richard > > > > Ted Roeloffzen-2 wrote: > > > > I've made a webapplication class that extends from > > AuthenticatedWebApplication in the wicket-auth-roles project version > 1.3.1 > > I've implemented the needed methods, such as getHomePage, > > getSignInPageClass > > and getWebSessionClass. They all return the appropiate class. > > On the homepage i've added the annotation: > @AuthorizeInstantiation(Roles.* > > USER*) > > > > but when i run the application and go to the URL, it goes directly to > the > > homepage and the loginpage isn't called. This isn't supposed to happen, > > because you need the user rol to get there. > > > > Does anyone have an idea about what i'm doing wrong? > > > > > > -- > View this message in context: > http://www.nabble.com/Wicket-auth-roles-problem-tp15631688p15632086.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
