Re: [Wicket-develop] WicketTester and AuthenticatedWebApplication

2006-08-28 Thread Jean-Baptiste Quenot
* Ingram Chen: > we shouldlet WicketTester just delegatecall to > targetApplcation. I believe it's possible but it will break > exist test because WicketTester is no longer a WebApplication > and things such as DummyHomePage will be not availiable... Right, we need t

Re: [Wicket-develop] WicketTester and AuthenticatedWebApplication

2006-08-22 Thread Igor Vaynberg
i guess a possible solution for appication stuff might look like an ibehavior but targetted for an application instead of a component.the testing is another matter. i started working on a test solution that allows testing by mocking wicketservlet instead of mocking application. but i didnt have any

Re: [Wicket-develop] WicketTester and AuthenticatedWebApplication

2006-08-22 Thread Ingram Chen
hmm... I agree with Quenot, we should let WicketTester just delegate call to targetApplcation. I believe it's possible but it will break exist test because WicketTester is no longer a WebApplication and things such as DummyHomePage will be not availiable... On 8/22/06, Juergen Donnerstag <[EMAIL PR

Re: [Wicket-develop] WicketTester and AuthenticatedWebApplication

2006-08-22 Thread Juergen Donnerstag
We have similar issues with XXXApplication. SpringApplication used to (but no longer) required init() code, AuthenticatedWebApplications does and in the future others may be added. I think an RFE exists already which asks for improvement. We haven't come up with a general solution though, a solutio