Java on the Drawing Board: Sun's BluePrints
Need to provide application access to disparate data sources, without having to change the business logic every time the data source changes? In search of a more efficient approach to handling large, read-only web lists? Or just plain tired of having to reinvent the wheel to solve each new Java design problem?
Maybe you need an introduction to Sun Microsystems' Java BluePrints programa resource collection of guidelines, best practices, design patterns, and actual code samples aimed at solving Java-specific design problems and helping developers shift their development projects into high gear. Launched in May 2001 and expanded over the years, the BluePrints initiative is Sun's effort to make life easier for harried Java developers struggling with complex enterprise applications and tight production cycles.
Who Should Use the BluePrints?
According to Walter Hurst, CTO of Wakesoft, Inc. (maker of the Wakesoft Architecture Platform that employs the Java BluePrints), any level of developer can benefit from using the BluePrints. "A novice Java developer can get some ideas about how professionals solve problems. The intermediate developer can refine his or her techniques. And expert developers can use the patterns to make sure the team is doing things in a certain way, and get into minute detail as to how Sun is solving specific [design] problems," he says.