Or several. It depends on how good of a model you want of a 'real' web server with separate web server and database, plus separate test system to drive the load. I wouldn't spend money for it from scratch, but if you already have recent hardware in a small form factor it would be worth considering.
So you have irrefutable evidence that global warming is due to fossil fuel combustion products and not, say, the output of the sun?
Yes, pretty much. Hardly anything is totally "irrefutable", but there is plenty of evidence which supports the link between warming and CO2, including the paleoclimate record, the observed timing, rate, and magnitude of the warming compared to the CO2 forcing (when other forcings are included too, of course), the stratospheric cooling fingerprint, the observed changes in the diurnal cycle, etc.
Al Gore's cartoons notwithstanding, C02 levels follow warming trends rather than precede them. So any linkage cannot be attributed to cause.
Furthermore, we have not seen any further warming since 2001. That's a 7 year pause in warming that cannot possibly be attributed to decreases in fossil fuel consumption.
So, no there is nothing even close to irrefutable much less insinuating a human-caused warming trend.
Personally, I find it absurd that anyone could put their faith in a global cooperative government solution to global warming. Governments are good for one thing - that is to break your leg, hand you a crutch and exclaim "See, if it weren't for us, you couldn't walk!"
If man really is the cause of warming, it won't be the governments that reverse the trend.
Log4j supports selective logging. That means you can have info/debug/trace priority messages in place, but never see them in the log unless you explicitly enable extra logging for that class or package. You can do this at runtime, e.g., via something like 'chainsaw' (which attaches to a running process) or hooks in your UI.
Our policy is that logs are usually very quiet. Application startup/shutdown and not much more. But if there's a problem the debugging messages are already in place to let us peak into the system, even if it's been deployed to a production site.
BTW AOP is also great for this. You can configure logging interceptors that log activity when you're in a development environmnent, but easily removed in production. This is a natural approach when going from one layer to the next, e.g., when wrapping the DAO layer.
Somebody ought to cross ball point pens with coat hangers so that the pens will multiply instead of disappear.
