Thanks, Erik, that code would do the trick, too. I've implemented
a different workaround, though. In the next release of wicket (1.4.8),
WicketSessionFilter will 'expose' both the session and the application, Igor
already resolved my JIRA Issue [1]. BTW: Thanks to Igor for picking that
up so
That sounds great. Could you update the wiki page with the specifics for
Wicket 1.4.8?
Regards,
Erik.
Op 17-03-10 08:20, Jonas schreef:
Thanks, Erik, that code would do the trick, too. I've implemented
a different workaround, though. In the next release of wicket (1.4.8),
I just reviewed the code Igor for the fix Igor implemented [1], and I
don't think
it will be a drop-in replacement for the code in the wiki, since it only exposes
the application if there's an active HttpSession. The code from the wiki on the
other hand always exposes the Application.
In the patch
whats the use of having an application object if there is no session object?
-igor
On Wed, Mar 17, 2010 at 6:03 AM, Jonas barney...@gmail.com wrote:
I just reviewed the code Igor for the fix Igor implemented [1], and I
don't think
it will be a drop-in replacement for the code in the wiki,
Hi Jonas,
Perhaps this is what you need:
http://cwiki.apache.org/WICKET/springbean-outside-wicket.html
Regards,
Erik.
Jonas wrote:
Hi all,
we're using WicketSessionFilter in our product to access
our custom WebSession, which works fine. Now we've tried
to also access the
I create a JIRA issue for this:
https://issues.apache.org/jira/browse/WICKET-2778
cheers,
Jonas
On Thu, Mar 11, 2010 at 1:10 PM, Jonas barney...@gmail.com wrote:
Hi all,
we're using WicketSessionFilter in our product to access
our custom WebSession, which works fine. Now we've tried
to also
Hi all,
we're using WicketSessionFilter in our product to access
our custom WebSession, which works fine. Now we've tried
to also access the org.apache.wicket.Application (e.g. using
Session#getApplication or Application#get), which doesn't seem
to work, because the application isn't bound to the