Javaโข Enterprise Best Practices
โ Scribed by Robert Eckstein, J. Steven Perry, O'Reilly Authors
- Publisher
- O'Reilly Media
- Year
- 2002
- Tongue
- English
- Leaves
- 288
- Edition
- 1
- Category
- Library
No coin nor oath required. For personal study only.
โฆ Synopsis
Until Java Enterprise Best Practices, advanced Java developers relied on the advice of a loose-knit community of fellow developers, time-consuming online searches for examples or suggestions for the immediate problem they faced, and tedious trial-and-error. But Java has grown to include a huge number of APIs, classes, and methods. Now it is simply too large for even the most intrepid developer to know it all. The need for a written compendium of J2EE Best Practices has never been greater. Java Enterprise Best Practices focuses on the Java 2 Enterprise Edition (J2EE) APIs. The J2EE APIs include such alphabet soup acronyms as EJB, JDBC, RMI, XML, and JMX.
๐ SIMILAR VOLUMES
Java developers typically go through four "stages" in mastering Java. In the first stage, they learn the language itself. In the second stage, they study the APIs. In the third stage, they become proficient in the environment. It is in the fourth stage --"the expert stage"-- where things really get
Java Database Best Practices rescues you from having to slog through books on each of the various APIs before figuring out which method to use! This guide introduces each of the dominant APIs, explores the methodology and design components that use those APIs, and then offers practices most approp
When creating complex Java enterprise applications, do you spend a lot of time thumbing through a myriad of books and other resources searching for what you hope will be the API that's right for the project at hand? Java Database Best Practices rescues you from having to wade through books on eac
Assuming a familiarity with SQL and at least one Java enterprise API, this book describes the different approaches Java provides for database programming, assesses what approaches fit which problems, and recommends best practices for each model. The author discusses data architecture, transaction ma