Re: Bug with setResponsePage and PageParameters for wicket 1.4.6?

I think it is a know bug (http://issues.apache.org/jira/browse/WICKET-2717) and was is already fixed in trunk. Hopefully there will be a 1.4.7 release very soon. Alex Objelean fatefree wrote: I noticed something strange, I have a search panel on all pages that contains a single form like

Re: Ajax editable image @L

Juan's approach works, but I found myself reimplementing some of AxajEditableLabel event-handling code. So, I tried another approach where I create a panel with two fragments pictureFragment and uploadFragment. I then add an AxajEditableLabel to the panel which would ideally override newLabel(..)

AbstractAjaxTimerBehavior#onTimer() doesn't work in deployment mode

Hi, I'm using wicket 1.4.6 and saw that the onTimer method of an AbstractAjaxTimerBehavior object isn't called, when I switch vom development mode to deployment mode. This happens also with wicket 1.4.5. Is there something I need to do to get it working in deployment mode? In addition, after

Wicket best practice

Hi, I am trying to write a code generator (using Clickframes code generation framework) which would generate a fully working Wicket project directly from the Spec. Is there a document which describes the best practice for folder/package structure in a wicket project. To write the code generator,

Re: Wicket best practice

Vineet, very cool stuff you are wooing on. As for best practices with regard to layout, there is actually a Maven Wicket archetype that would probably answer those questions well. From what I remember its pretty straight forward maven web layout. And yes, HTML and Java source are in same main

Re: Wicket best practice

Thanks. I will look at the maven archetype. More than just pages, I am looking at links, forms, inputs etc. For example, to create a link I am either use a href= in the HTML, or I can use Wicket link component model, what's the difference and which one should I use? Btw, my goal is to

Re: Wicket best practice

There are 2 main ways to create a link with Wicket: 1. Use autolinking. wrap your link in wicket:link tags in the HTML and take note of package structure, so if in same package HomePage.html would go in href, and if its in a package called admin, you'd have admin/AdminHomePage.html, etc. 2.

Re: How to write a testcase for CheckGroupSelector.

vermas wrote: How to write a testcase for CheckGroupSelector. Try http://wicketpagetest.sourceforge.net/ which supports execution of Javascript in the tests. - -- Kent Tong Better way to unit test Wicket pages (http://wicketpagetest.sourceforge.net) Books on CXF, Axis2, Wicket, JSF

Re: Wicket best practice

Thanks. Is one approach better than the other? Vineet On Sat, Feb 6, 2010 at 5:00 PM, Andrew Lombardi and...@mysticcoders.comwrote: There are 2 main ways to create a link with Wicket: 1. Use autolinking. wrap your link in wicket:link tags in the HTML and take note of package structure, so

AbortException

I may be using this wrong, but my understanding was that if I wanted to redirect a user and hault execution of the current page I could do the following: setResponsePage(LinkPartners.class); throw new AbortException(); However, there seems to be situations where the AbortException actually