wicket

I have used the jQuery AJax call to send JSON as documented here in StackOverflow The problem is that I am not receiving any Data on the server . I can see that the call did reach the target ajax behavior -- but in onRequest() method , the RequestCycle dd not contain any parameters My Wicket Code: AbstractAjaxBehavior ajaxSaveBehaviour = new AbstractAjaxBehavior(){ private static final long serialVersionUID = 1L; @SuppressWarnings("unchecked") public void onRequest() { //get parameters final RequestCycle requestCycle = RequestCycle.get(); final PageParameters pageParameters = new

I've been working with Wicket for month or two now, making simple web applications with it and getting used to models and so forth. Now I'd like to move forward and see if I can put what I've learned so far to use and create a medium/large web application. However, I haven't spent much time thinking about how to make pages stateless. If I understand correctly, making a stateless page is achieved by making the page bookmarkable and making sure that no stateful components are added to the page. For the website I am making I want to avoid "Page expired" messages, let users be logged in via

Given the various advantages of the Scala language I have decided to write my next web-application in Scala. However, should I be using Wicket or Lift? I am familiar with Wicket, and like it quite a bit, but know very little about Lift. Is learning Lift worth the effort in this context? In order words, how does Lift compare to Wicket? Given that the web-app will be in Scala, could using Lift make my life as a developer easier? If you like Wicket, you should stick with what you know & like. Wicket is a fine web framework and doing Scala & Wicket is very nice because you can use Scala's traits

How do I redirect to another page using Wicket? IIRC, some exception has to be thrown in the constructor, but I don't remember which one. Thanks in advance. Throwing a RestartResponseAtInterceptPageException will do it, as you noted in your own answer, but that's really part of a system for allowing a redirect with an eventual continuation at the current page (frequently part of an authorization process). If that's not your situation, but you still have to do something that interrupts processing, it might be better to throw a RestartResponseException . The principal usage that I know of for

I am using Wicket with the Wicket Auth Project for my presentation layer and I have therefore integrated it with Spring Security. This is the method which is called by Wicket for authentication for me: @Override public boolean authenticate(String username, String password) { try { Authentication request = new UsernamePasswordAuthenticationToken( username, password); Authentication result = authenticationManager.authenticate(request); SecurityContextHolder.getContext().setAuthentication(result); } catch (AuthenticationException e) { return false; } return true; } The contents (inside ) of my