On 2/18/07, Johan Edstrom <[EMAIL PROTECTED]> wrote:
Hi,
I just ran into an issue with the JMX in trunk, it is now enabled by
default.
I'm porting an existing webapp, and was interested in the latest Wicket
tools.
Since this existing resource I rely on already exposes JMX and MBeans I
really would like to be able to 'turn off' the JMX implementation in Wicket.
Yep, you're right. It's not relevant for 1.3 as it's a separate
project there, but for 2.0 we could/ should make it a separate setting
or make it a separate project like it is for 1.3
Eelco
