For a class that has an empty constructor and all it's initialization code in the boot() method, is the boot method the appropriate place for initialization which isn't strictly associated with booting the service as well, or is it okay to put an object initalization in the constructor?
Case in point: java/engine/org/apache/derby/impl/store/raw/data/BaseDataFileFactory.java It has an empty constructor, and a big boot() method. Strictly, the constructor isn't quite empty, a few of the members are declared like this: private long nextContainerId = System.currentTimeMillis(); The compiler moves the initialization to the constructor, so it isn't really as empty as it looks. This isn't a big deal, but I'm curious to know if there is an existing convention here that should be adhered to, or if doing the natural thing (using the constructor) is okay. =) -- Anders Morken My opinions may have changed, but not the fact that I am right!
