Do you know if this is fixed in beta 3?
On 3/31/06, Juergen Donnerstag [EMAIL PROTECTED] wrote:
Modify AuthenticatedWebApplication.java yourself. If your using the
jar, than copy AuthenticatedWebApplication.java, make the changes, add
it into the appropriate package in your own project and the
yes it should be.On 4/3/06, Andre Matheus [EMAIL PROTECTED] wrote:
Do you know if this is fixed in beta 3?On 3/31/06, Juergen Donnerstag [EMAIL PROTECTED] wrote: Modify AuthenticatedWebApplication.java yourself. If your using the
jar, than copy AuthenticatedWebApplication.java, make the changes,
When I tried to use AuthenticatedWebApplication instead of
WebApplication to create my Application, the system started to give me
an error: wicket.WicketRuntimeException: Use Application.init() method
for configuring your application object
The constructor of my Application is the following:
It obviously hasn't been changed yet. The code from
AuthenticatedWebApplication() must be moved into its init() method.
Juergen
On 3/31/06, Andre Matheus [EMAIL PROTECTED] wrote:
When I tried to use AuthenticatedWebApplication instead of
WebApplication to create my Application, the system
It obviously hasn't been changed yet.
OK, fine.
If I understood correctly it is not possible to use nor to test the
packages wicket-auth-roles-1.2-beta2 and
wicket-auth-roles-examples-1.2-beta2 as they are now. Am I right? Or
there are other ways of using them without the
Modify AuthenticatedWebApplication.java yourself. If your using the
jar, than copy AuthenticatedWebApplication.java, make the changes, add
it into the appropriate package in your own project and the
classloader will find it before the one in the jar
Juergen
On 3/31/06, Andre Matheus [EMAIL
