This article contains a collection of short, punchy audio recordings made at JavaOne on Thursday, May 18, 2006. Each recording captures one person's notion of an idea that is important for developers to think about.
This article contains a collection of short, punchy audio recordings made at JavaOne on Wednesday, May 17, 2006. Each recording captures one vendor's notion of an idea that is important for developers to think about.
Ed Burns is co-specification lead for JSR 252, JavaServer Faces 1.2, and Jan Luehe leads JSR 245, Java Server Pages 2.1. Artima interviewed the two spec leads about new JSF and JSP features included in Java EE 5. Burns and Luehe discuss the JSP and JSF common expression language, AJAX, and the role annotations play in dependency injection.
This article contains a collection of short, punchy audio recordings made at JavaOne on Tuesday, May 16, 2006. Each recording captures one vendor's notion of an idea that is important for developers to think about.
Clustering emerged in recent years as the most important system architecture supporting highly available and scalable systems. This article, part of Artima's ongoing Innovative Architectures series, describes how Jini technology lays the foundation for dynamic clustering, while also reducing ongoing cluster maintenance and system administration.
by Frank Sommers, December 6, 2005, 1 comment
The first in an occasional Leading Edge Java series on innovative architectures, this article describes a distributed system design that extends J2EE with Jini tehnology to help manage banking devices in a cost-effective and decentralized manner.
The Java Contactless Communication API enables mobile devices that communicate via short-range wireless means, such as RFID, infrared, or Bluetooth, to exchange data. This article explains the role of this new API in emerging near-field communications, and includes an example of reading data from any contactless target, such as an RFID tag.
In this audio broadcast, nine JSR spec leads and other Java and JCP luminaries discuss issues of the Java Community Process and Java standards.
JDBC 4 is the forthcoming release of the Java Database Connectivity API. Currently in Early Draft Review in the JCP (JSR 221), JDBC 4 is a major new release with a strong focus on ease-of-use and programmer productivity, and support for SQL 2003 data types, including SQL's native XML type. This article surveys the key JDBC 4 features.
by Bill Venners and Frank Sommers, August 23, 2005, 2 comments
In this audio interview, Gavin King, founder of the Hibernate project, discusses the relationship between Hibernate and EJB3, various strategies for collection fetching, why transparent persistence is a bad idea, and the role of caching in persistence architectures.
Java Business Integration (JSR 208) defines container services that enable system integration via Web service technologies and XML message exchanges. In this interview, JBI Spec Lead Ron Ten-Hove discusses how JBI will impact enterprise Java developers.
by Frank Sommers with Bill Venners, August 2, 2005, 6 comments
In this audio interview, Onno Kluyt, chair of the JCP, discusses what the JCP has learned from open source, what open source could learn from the JCP, the JCP's attitude on overlaps between JSRs, and the JCP's "choir of angels."
The Java Data Mining API promises to bring to data mining what JDBC brought to databases, and to make data mining a new and useful part of an enterprise Java developer's tool chest. This article introduces basic data-mining concepts, and illustrates sample JDM code to model customer behavior.
Java's future hinges as much on leadership as on sound technology. In this article, the spec leads of several JSRs share their insights into the key ingredients of leading a successful project. Substitute spec lead with project lead, and these lessons are relevant to anyone leading a software development effort.
In this interview, Erich Gamma, co-author of the landmark book, Design Patterns, talks with Bill Venners about the development process used by the Eclipse team, the team's "culture of shipping," and the importance of transparency in building community around a product.