In the previous article, we explored Hibernate, a popular Open Source O/R Mapping framework for J2EE-based enterprise applications. Hibernate automates to a large extent the creation of an efficient persistence layer for the enterprise application. Hibernate makes mapping objects to be persisted to underlying database easier. In other words, Hibernate allows representing an underlying database by using simple Java objects and vice versa.
FrogPad’s gone sinister, the Pragmatic Programmers get automated, Zero G’s InstallAnywhere now does Windows, and DataSource unveils Jetson, its new J2EE app generator. Supporting diverse and differently abled users is no longer a frill, it’s a minimum requirement. Still … left-handed frogs? Actually, the Left-Handed FrogPad is intended not for amphibians, but for Homo Sapiens Southpaws. It’s a one-handed keyboard that minimizes chording in favor of a meta-key selection strategy, and it’s laid out to maximize both ease of learning and typing convenience.
In this article, I'll explain how to avoid some common pitfalls that occur when internationalizing J2EE applications. I'll also give a brief overview of internationalization and show where to find more information on the topic. What is Internationalization? The Encoding of Parameters. Setting the Charset. Ignoring Your Default Locale. Further Reading
This article begins with high-level definitions of portals, portlets, and portlet containers. Following that, we will highlight the most important aspects of the Java Portlet Specification. Later this month, a follow-up article will demonstrate how to develop a portlet from scratch, reinforcing the concepts described below.
Last month, Mike Loukides, a senior book editor for O'Reilly, wrote an editorial complaining that Sun has blocked attempts to have JBoss -- a popular application server based on the J2EE specifications, developed under the open source GNU Lesser General Public License -- undergo certification. In that piece, Loukides called on Sun to \"... establish a level playing field in which all Java developers, regardless of their funding or licensing requirements, can participate.
Shortly after the release of JRun version 3.0, Allaire Corp. (now Macromedia, Inc.) announced a strategic alliance with Sun Microsystems, formally licensing Sun's Java 2 Enterprise Edition (J2EE). Part of our commitment to the J2EE standard is ensuring the compatibility of JRun with the J2EE Compatibility Test Suite (CTS). The CTS is a comprehensive set of over 5,000 tests and helps to ensure that JavaServer Pages (JSPs), servlets, and Enterprise JavaBeans (EJBs) run in a manner that ensures compatibility with other J2EE-branded application servers. Version 3.1, which is currently in Beta, represents the first CTS-compatible release of JRun.
XDoclet is a template-driven development tool that allows developers to generate code, configuration files, or even documentation. This article will demonstrate how to download, install, configure, and use XDoclet to take the drudgery out of writing J2EE code.
There are five more weeks of winter (at least here in the Northern hemisphere). That thought helps explain the overcast skies. While you're stuck inside (or, if you're enjoying the Southern hemisphere, after a long day of playing in the sun), here's what's new on ONJava this week.
The second edition of Java Enterprise in a Nutshell includes an enormous amount of new material, reflecting the significant milestones that enterprise Java has achieved since the first edition was published in 1999. These milestones include the release of the full J2EE 1.2 spec in December 1999, the release of the J2EE 1.3 spec in the summer of 2001, the recent wave of Java support for Web services, and numerous other achievements in between. In this article, I'll highlight just a few of the powerful new features found in the Java enterprise APIs that are described in the second edition.
W3C the World Wide Web Consortium,published the XML 1.0 specification on February 10th, 1998. The XML 1.1 specification was published six years later, on February 4th 2004. In the six years, XML has taken the industry by storm. XML has become the standard for how to describe and exchange data. The current development platforms, .NET and J2EE, support XML natively. All modern enterprise applications, be it a SQL Server or Oracle database, a BizTalk Server, an Office suite, or any of the other thousands of applications support XML to various degrees. You will be pretty hard pressed to find an application that does not support or use XML.
