Elizabeth Blair

Subscribe to Elizabeth Blair: eMailAlertsEmail Alerts
Get Elizabeth Blair: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn

Top Stories by Elizabeth Blair

While J2EE technology is designed to support portability, it's always possible to write nonportable code. In Part 2 of this series, we (the BluePrints development team) offer recommendations on how to avoid specific design, implementation, and deployment pitfalls that can compromise portability. A comprehensive collection of the J2EE BluePrints application programming model can be found at http://java.sun.com/j2ee/blueprints. This month, our recommendations are: Deploy each Web application with a unique context root to avoid colliding with other applications. Use handles or remote object references to store session state in HttpSession. Be aware of changes in taglib DTD from J2EE 1.2 (JSP 1.1) to J2EE 1.3 (JSP 1.2). Always import all classes used in a JSP. Never throw resource-specific exceptions from BMP code. Wrap authentication code in helper classes. Always co... (more)

Build To Spec!

Many J2EE 1.2-based applications and components are emerging in the marketplace as the J2EE platform matures. Application portability is one of the most important benefits offered by the J2EE platform. Through the J2EE Java Pet Store sample application, the J2EE Blueprints team has developed a set of best practices for ensuring application portability across J2EE-compatible application servers. This article is the first in a series of J2EE application and component portability recommendations for the J2EE development community. This series will focus J2EE application portability... (more)