Java 1.4 has just been released. This is a major new release, with 62 percent more classes and interfaces than Java 1.3; needless to say, there are lots of new features. This article describes my personal favorite top ten new features, ordered from cool to extremely cool. You can learn more about all of these features in the 4th edition of Java in a Nutshell. Note that the new features I've selected for this article are drawn from those documented in that book; thus I do not include any new graphics and GUI features or new enterprise features.

Every now and then, we need to build a custom client/server model, especially if we are students and are required to submit some network project using Java's powerful network programming capabilities. In this article I attempt to provide a pattern/framework for developing custom client/server programming using the Java language. This article is divided into two parts: server development and client development.

This article helps J2EE developers better understand the class loading architectures of a variety of application servers and how the components of a particular J2EE application are loaded. Armed with this information, J2EE developers can design portable J2EE packaging structures or at least understand the tradeoffs when using proprietary techniques. This is particularly important for J2EE component and framework providers who must take on the extra task of shipping their components in the most portable manner.

You may have come across a situation where you need to cache some data in your server. You then use this cache to service queries from incoming requests. You will also probably have a thread that listens for cache update events. This thread updates the cache in response to these events.
This leads to a problem as it's unlikely that both the threads servicing requests and the update thread will be able to use your cache simultaeneously. You may be tempted to use an exclusive lock such as a Java synchronised block to handle this. This will work but it is probably the worst way that you can do this from a performance perspective. This articles shows how you can use reader writer locks to accomplish the same thing using a much more efficient technique.

The Java 2 Platform, Standard Edition (J2SE) 1.4 has introduced several new features and enhancements for Object Serialization, Remote Method Invocation (RMI), Common Object Request Broker Architecture (CORBA), and networking in general. The new features and enhancements either address some changes in standard specifications such as CORBA, or improve the performance of existing features. This article gives an overview of the new features and enhancements.

JNDI, the Java Naming and Directory Interface, is a fundamental component of J2EE (Java 2 Platform, Enterprise Edition) and any J2EE application. However, since JNDI does not depend on any other J2EE technologies, and the JNDI client interfaces are part of the J2SE (Java 2 Platform, Standard Edition) distribution, J2SE applications can also exploit JNDI's benefits. In this article, Brian Goetz explores basic JNDI concepts, how JNDI is commonly used, and how to configure a free JNDI provider for use with J2SE applications. (1,600 words; April 19, 2002)

As a Java developer, you should be aware of the tremendous wealth of open source development software that is available for your use -- even if you have no desire to release any of your own software as open source. In this article, I will introduce you to some of the most useful open source Java development tools by showing you how I used these tools to develop a complete database-driven Web application called Roller...

Java 2 Platform, Enterprise Edition (J2EE) and .Net are competing technologies that both contribute to Web service creation. In this article, Jonathan Lurie and R. Jason Belanger describe a Web service and compare J2EE's major components with .Net's. With this ammunition, you can power your way through a conversation concerning how Web services will benefit your department's strategic direction. (2600 words)
In closing, we suggest you build a Web service with both .Net and J2EE. You will quickly know which platform works best for you. In selecting a vendor, many people concede to the following rule of thumb: if you are committed to a homogenous Microsoft platform now, then choose .Net, otherwise choose J2EE.

The Java 2 Enterprise Edition (J2EE) Platform is defined by four key pieces: the specification, the reference implementation, the compatibility test suite, and the BluePrints program. BluePrints describes the best practices and design guidelines for a distributed component architecture. This article introduces an eight-step J2EE development methodology based on the Rational Unified Process and the BluePrints sample application. By reading this article, you will better understand many important J2EE architecture topics, and be able to apply that knowledge to extend and modify this simple methodology to solve your special business problems. (3,600 words)

Un très bon article vient de paraitre sur le site de Sun concernant les nouvelles capacités de Drag & Drop et de Copier/Coller de Java 1.4.

Les anciens codes seront toujours fonctionnels, mais pourront etre grandement simplifiés. C'est toute l'architechture des transferts de données avec le presse-papier qui a été refaite. Elle est maintenant bien plus puissante, et fourni une moyen de développer des applications puissantes, rapidement et simplement.

In this tutorial we become familiar with the basic security architecture of Web Services. For those unfamiliar with the concepts, we review symmetric and asymmetric security protocols, identity, SSL and GSS-API. We review the options open to developers using Web Services, and make the case for more advanced systems based on the GSS-API framework. We then demonstrate a simple security system on a Web Service.

In this fourth part of the Web services tutorial, we learn about two ways to integrate Web services with J2EE. We introduce the basic wrapper Web service and the transparent integration framework and explain the situations in which each approach provides substantial advantages. We also show how SOAP messages can be sent over the JMS protocol.

• J2EE, c'est un standard ?
• Pour quelle finalité ?
• Où en est-on dans la pratique ?
• Cette spécification ne concerne-t-elle que les serveurs d'applications ?
• Quel rapport avec Java et les EJB ?
• Qui est aux commandes de J2EE ?
• Où en est-on dans les versions de J2EE ?