JMS Application Changes Under J2EE
As more and more application servers that comply with the new J2EE 1.4 spec become available, Java developers will have to consider how -- and if -- they should migrate their J2EE 1.3-compliant code. In this article, David Currie takes a look at the changes to one particular area of the J2EE specification: messaging. You'll see what you'll need to change, what you can leave as is, and what new opportunities await you.
- Visit Site:
- JMS Application Changes Under J2EE
- Filed in:
-
Java / Magazine Articles / Miscellaneous
- Date Added:
- May 13, 2004
- Last Updated:
- May 15, 2004
License and Pricing Information
| Publisher site visits: | 776 |
|---|---|
| Average rating: | 0.00 |
| Total ratings: | 0 |
Publisher Info
- Author:
Other listings by this publisher
- Using Aspect-Oriented Programming to Maintain Legacy Java Apps
- Tracing in a Multithreaded, Multiplatform Environment
- Unclogging Server Bottlenecks w/ Active Containers
- Java 2 Platform and JAAS Authorization Architectures
- Data Management in J2EE Apps
- Mobile Database Access
- Introduction to Jena
- Use the Element Construction Set to create formatted logs
- Introducing the Reflexive User Interface Builder
- Generate Certificate Chains for Testing Java Applications
- The On Demand Operating Environment
- Dynamic Web Data Analysis: A Design Approach
- Java Performance Tuning w/ Fat Clients
- Annotations in Tiger (J2SE 5.0)
- Adding JRuby to your Java Toolbox
- A Look at Binary Runtime Environment for Wireless (BREW)
- RAD Tutorial w/ JavaServer Faces and WS Portal
- Swing Dev with TableModel Free framework
- JDK More Flexible, Scalable Locking
- Wireless messaging with JXTA
- Intro to Java Tutorial
- Secure a J2ME Environment with JCE
- Concurrency in JDK 5.0 Tutorial
- Building Web Services w/ Eclipse Tutorial
- Portlets with FacesClient Components
