we already have that but it is not in the filter because the filter doesn't have anything to do with that kind of stuff its in
WebApplication.getSessionAttributePrefix(final WebRequest request) (dont know why it needs the request param) and then appended with: Session.SESSION_ATTRIBUTE_NAME that makes the key. The problem is that in WicketSessionFilter we can't call that WebApplication method. maybe we can refactor it a bit to make it more clear so that WebApplication gets a static method that gets only the filtername johan On 9/1/07, Thomas Singer <[EMAIL PROTECTED]> wrote: > > Ah, that's the secret missing link. I then suggest to have a method > getSessionKey(String wicketFilterName) which is used by the "normal" > WicketFilter to read/write and the WicketSessionFilter to read the > WebSession. > > Thanks, Eelco! > > -- > Cheers, > Tom > > > Eelco Hillenius wrote: > >> No, my confusion is about how it comes into the HttpSession accessible > under > >> the attribute name which is build only in WicketSessionFilter (aren't > the > >> HttpSession's attributes not a simple string-to-object map so you need > the > >> right key to get the value?). > > > > That's why you need to provide the filterName argument when setting up > > the filter. The filtername is used as the key by the actual Wicket > > application, so if you set the filterName to the name of the filter > > you want to get the session from, the two keys match. > > > > Eelco > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
