n the Java market, “write once, run anywhere” standardization is the carrot and the threat of .NET adoption is the stick. Which is the greater motivator depends on the vendor’s
erhaps the single biggest challenge in writing Java applications is dealing with UI issues. Regardless of the application’s power and flexibility, people will always want it to look familiar?to look
SL (eXtensible Stylesheet Language) enables you to transform an XML document into HTML, another XML document, or any plain text. Using XML with XSL separates the business logic data from
elieve it or not, the Jet Propulsion Laboratory (JPL) from NASA is actually developing Java capabilities. The JPL is a division of NASA responsible for the robotic exploration of the
J2EE takes the hassle out of distributed programming, but there’s a catch. Although you no longer have to contend with such low-level issues as threading, synchronization, or persistence, you also
uild a Java Web Application Using HttpUnit and Test-driven Methodology, Part I showed how HttpUnit complements the JUnit functionality to provide testing capability for Web applications, which ordinarily are difficult
ometimes Java classes seem like close relatives who unfortunately don’t have the same parent. Their structures and looks are similar, but not so similar that you can derive one from
Unit performs automated testing for standalone Java applications that either run on the command line or serve as components. If you develop large-scale or distributed applications, however, you are most
ava programmers who use JDBC may presume that the technology is restricted to interaction with database products such as IBM DB2 Universal Database, Informix, Oracle, or Microsoft SQL Server. This