No error/warning is reported when Proxool is unable to
instantiate the LogFactory specified by the system
Logged In: YES
If a LogFactory is "forced" by the system property, then I
believe Proxool should just throw an exception if it cannot
Currently, Proxool will ignore it and continue its discovery
process. According to me, this is not the right behavior since
Proxool wasn't able to do what is has explicitly been asked. In
this case, throwing an exception is probably the right
This bug is invalid!
Proxool will actually throw an exception and won't start...
Anyway, the error should be detected a bit earlier and a
cleaner exception thrown.
This bug is declared invalid.
(sorry for the noise)