<EM>Grab your marshmallows and a stick and gather 'round the campfire for some Java stories. The Ranch writers won't be winnin' any literary prizes, that's fer sure. But ya still might learn a thing or two.</EM>
You too can learn one of the most powerful concepts in all of OOP-land.
Prerequisite: Understand Classes, Objects and References
Better Enterprise/Network Monitoring with Component Diagnostics[/url]
When Captain Picard asks for a Level 3 diagnostic, what, exactly, does that mean? If your component goes stupid, do you want to fix it before your boss finds out? The alternative might be users calling customer service, calling the veep who calls your boss who ... well .... you get the idea.
So you need to check your code in, but when you do a "get latest" on version control, the build breaks. You check with the guy that checked in the stuff that doesn't work and "well, it works for me!" -- he's checked in some environment stuff that works on his system, but not yours. There are some solutions, but ... a lot of those solutions have worse problems! This article explores several different lousy solutions and recommends a hybrid solution - not perfect, but a big improvement!
Prerequisites: having worked in a multi developer environment.