thanks igor
On Mon, Aug 3, 2009 at 10:30 AM, Igor Vaynberg wrote:
> it looks like you are not setting the filterName attribute of the
> session filter to the name of the wicket filter. because of that it
> cannot find the correct application object.
>
> -igor
>
> On Mon, Aug 3, 2009 at 10:25 AM,
it looks like you are not setting the filterName attribute of the
session filter to the name of the wicket filter. because of that it
cannot find the correct application object.
-igor
On Mon, Aug 3, 2009 at 10:25 AM, Fernando
Wermus wrote:
> Wicket 1.3.6
>
> This is the line
>
> se
Wicket 1.3.6
This is the line
sessionKey = application.getSessionAttributePrefix(null) +
Session.SESSION_ATTRIBUTE_NAME;
On Mon, Aug 3, 2009 at 10:11 AM, Igor Vaynberg wrote:
> what version of wicket are you using? for me line 158 is "}"
>
> -igor
>
> On Mon, Aug 3, 2009 at 9:59
what version of wicket are you using? for me line 158 is "}"
-igor
On Mon, Aug 3, 2009 at 9:59 AM, Fernando
Wermus wrote:
> Hi all,
> I am using wicket and blazeds. The users logs in through wicket and they
> use blazeds services as well. I need to verify in MessageBrokerServlet
> (blazeds ser
Hi all,
I am using wicket and blazeds. The users logs in through wicket and they
use blazeds services as well. I need to verify in MessageBrokerServlet
(blazeds servlet) that the user has logged in. Then I added the
WicketSessionFilter to get the session. But I got a null pointer exception:
ja