[wicketstuff-dashboard] Thread-Safe Dashboard Initialization

[newgro]

[wicketstuff-dashboard] Thread-Safe Dashboard Initialization

[solomax]

I don't have such problems
You can easily create your own WidgetFactory and register it in DashboardContext ...

[newgro]

Ok. I do that already. I only thought that this could be "fixed" in original code especially because the DefaultWidgetFactory is not extensible like protected loadClass(String widgetClassName).

But this way it is working and you could close the issue if no further action is planned.

[solomax]

I'm using "standard" web application (Jetty/Tomcat based) and this issue is not reproducible for me :(
Maybe widgets are being inited too early at your application?

[newgro]

I guess not. With using the CL of currentThread i get the appropriate beans injected.

[solomax]

@martin-g can you take a look at this?

[martin-g]

Maybe it should use application.getApplicationSettings().getClassResolver().resolveClass(String) ?

[solomax]

Thanks @martin-g :)
This looks much better

@newgro can you check if this will work for you?

[solomax]

@newgro I'll start the release process soon
Could you check if this application.getApplicationSettings().getClassResolver().resolveClass(String) code will work for you?