Magnus ?or Torfason <[EMAIL PROTECTED]> writes:
> I am thinking of a (possibly final) runInit() function in
> BaseInitable, that does nothing except call init() and register
> the fact that this service has already been inited. This would
> ideally be a separate init variable, not dependent upon SUCCESSFUL
> init, but only upon init being called.
Hmmm...you'd have to convince me that that's not over-engineering. :)
> ps. The logger code when initing is outputting rather untidy output,
> there is no \n at the end. I patched it up locally by hardcoding an \n
> in the calls to the logger, but this is obviously not the best way to
> solve the problem. (It's a small itch, and I won't scratch it for now,
> especially since I'm hoping that someone is already creating a Logging
> Service)
If you speak of the notice(String) method (which outputs via calls to
System.err's print() method), I added a newline terminator to its
output last night (by changing print() to println()). It helped out
the clarity of the error_log output a lot.
Daniel
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
