Build the enterprise with EJB 3, JBoss Seam, and Maven 2
Sure, it's possible to use Ant for enterprise builds, but here's the thing: You'll coax so much more mileage out of your EJB 3 and Seam-based projects by building them with Maven 2.
Michael Nyika, June 2008

Oracle focuses on app server, AJAX
Oracle's plate of announcements for the JavaOne conference this week features upgrades to its application server and IDE as well as a kit to make it easier to work with the Spring Framework for Java development.
Paul Krill, May 2007

XA transactions using Spring
Distributed transaction processing systems are designed to facilitate transactions that span heterogeneous, transaction-aware resources in a distributed environment. Using distributed transactions, an application can accomplish tasks such as retrieving a message from a message queue and updating one or more databases in a single transactional unit adhering to the ACID (Atomicity, Consistency, Isolation and Durability) criteria. This article outlines some of the use cases where distributed transactions (XA) could be used and how an application can achieve transactional processing using JTA along with the best of the breed technologies. The main focus is on using Spring as a server framework and how one can integrate various JTA implementations seamlessly for enterprise level distributed transactions.
Murali Kosaraju, April 2007

From Java EE security to Acegi
Application security as an enterprise-level concern needs to be carefully addressed by developers. This article compares the security services defined in Java EE and Acegi to help developers select the appropriate security services and program security from an enterprise-wide view.
Dr. Xinyu Liu, March 2007

The wise work manager for context-based scoping
This article examines the possibilities for high-performance Java Platform Enterprise Edition applications using context-scoped threads created by the application server with the Work Manager API.
Ravi Shankar Nair, Adrian Farolan, and Narendra Govindu, January 2007

A standardized object-relational mapping mechanism for the Java platform
Prior to the introduction of the Java Persistence API, no single persistence standard was available for both the Java SE and Java EE environments. Introduced as a part of Java EE 5, the Java Persistence API is a much awaited mechanism for persisting Java objects in the relational database by mapping Java objects to relational database tables.
S. Sangeetha, Anupama Nithyanand, S.V. Subrahmanya, January 2007

Book excerpt: Using WSIF for integration
The Web Services Invocation Framework allows BPEL business processes to access external resources natively. WSIF requires no modifications or extensions to BPEL code and makes BPEL more suitable for enterprise application integration.
Matjaž B. Jurič, December 2006

Book excerpt: Migrate to the Java Persistence API
In this article, an excerpt from Pro EJB 3.0: Java Persistence API (Apress, May 2006), authors Mike Keith and Merrick Schincariol discuss the issues of moving away from container-managed persistence to leverage the Java Persistence API and present strategies for achieving such a migration.
Mike Keith and Merrick Schincariol, August 2006

Migrating EJB 2.x applications to EJB 3.0
Enterprise JavaBeans 3.0 is a substantial change from the earlier specifications in terms of both the change in enterprise bean implementation models and in the bean location and call paradigm. How can you migrate legacy EJB code to utilize improvements in the new specification? This article discusses the strategies, both from a design and implementation perspective, for migrating existing EJB applications to the new specification.
Shashank Tiwari, August 2006

Develop enterprise Java applications with POJOs in Action
Many enterprise Java developers have discovered that Java EE's Enterprise JavaBeans framework causes more problems than it solves. POJOs in Action is a book that identifies these problems and presents an alternative based on plain-old Java objects and lightweight frameworks. In this article, Jeff Friesen reviews this book chapter by chapter.
Jeff Friesen, July 2006

JSF frameworks: Shale and Seam
JSF (JavaServer Faces) was created to address many of the shortcomings present in its Java Web-tier predecessors: JavaServer Pages (JSP) and servlets. But although JSF incorporates many novel approaches to developing Web-based applications from earlier technologies, bringing in a fresh approach to developing Java on the Web tier also comes with its share of challenges. To this end, two frameworks are already being used to streamline the use of JSF components in combination with other Java elements: Shale, developed by the Apache Software Foundation, and Seam, developed by JBoss. This article describes the value these two frameworks bring to your developments with JavaServer Faces.
Daniel Rubio, May 2006

EJB fundamentals and session beans
In this article, an excerpt from Beginning Java EE 5 (Apress, October 2005; ISBN: 1590594703), authors Jim Crume, Kevin Mukhar, James Weaver, and Chris Zelnak describe the benefits of using EJBs and focus specifically on how to develop a session bean.
Jim Crume, Kevin Mukhar, James L. Weaver and Chris Zelenak, February 2006

J2EE design decisions
In this article, an excerpt from POJOs in Action (Manning Publications, January 2006), Chris Richardson presents five questions developers must ask themselves when designing enterprise applications.
Chris Richardson, January 2006

Simplify enterprise Java development with EJB 3.0, Part 2
In Part 2 of this EJB 3.0 learning series, you learn how to develop data models using POJOs (plain-old Java objects), and how to transparently map those object data models to and from relational databases. Using EJB 3.0 annotated entity beans, developing database-driven applications is a breeze. Read the whole series on EJB 3.0: Part 1: Use annotations to develop POJO services Part 2: POJO persistence made easy
Michael Juntao Yuan, September 2005

Simplify enterprise Java development with EJB 3.0, Part 1
In this series of two articles, you learn how to develop simpler and more robust enterprise Java applications using the POJO (plain-old Java object) programming model in EJB 3.0. Runnable sample code illustrates the key elements in an EJB 3.0 application. In Part 1, Michael Juntao Yuan covers EJB 3.0 annotations to develop loosely coupled POJO applications and deliver container services to managed POJOs. Read the whole series on EJB 3.0: Part 1: Use annotations to develop POJO services Part 2: POJO persistence made easy
Michael Juntao Yuan, August 2005

All

 

We're hiring Senior Software Consultants! Come work for the fastest-growing Agile consultancy in the mid-Atlantic region! - Stelligent

About Us | Advertise | Contact Us | Terms of Service/Privacy

Copyright, 2006-2008 Network World, Inc. All rights reserved.