Done, I've just included a small project with a form and a submit link as well as a unit testcase to highlight the problem. They are not unit test cases for WicketTester as such, I would have to spend a bit more time poking around the code to know how to write a proper test for the tester...
Thanks again, Simon On 05/09/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote: > > * wicket user: > > > I've raised the issue, https://issues.apache.org/jira/browse/WICKET-932 > > Thanks! > > > Jean, please excuse my ignorance but when you request a quickstart > project > > do you mean you want the whole quickstart project with the problem > > illustrated zipped into my file. > > Anything that helps us to go straight to the problem can be > helpful. > > This can be: > > * A Java project with pom.xml, jetty launcher and relevant > sources. This is probably not really the best thing to do for the > problem at hand > * Unit tests, this is especially useful if the problem is about > WicketTester itself > > It is preferrable to submit the unit tests as a patch to the > existing Wicket test classes, but if you file whole classes, that > will do it as well. > -- > Jean-Baptiste Quenot > aka John Banana Qwerty > http://caraldi.com/jbq/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
