| Home : Java : J2EE |
| Click "Subscribe" if you want to be notified of new or updated links in this category. | Subscribe |
|
|
J2EE Listings
|
|
Total:
100 | Displaying: 11 - 20 | Pages: << 1 2 3 4 5 6 7 8 9 10 >> |
|
|
|
This article is the first in a two-part series that will concentrate on the resource adapter modifications and enhancements, with special focus on the new system-level contracts, particularly the lifecycle management and work management contracts. I'll cover implementation details and specification requirements, and we'll examine some pseudo-code to see how an EIS vendor might implement the new contracts for a version 1.5-compliant resource adapter. Part Two of this series (coming soon) will concentrate on the transaction inflow and message inflow contracts.
Updated: 05/18/2005
|
|
|
The aim of this article is to introduce small/medium size Web-based applications and propose a simple J2EE-based architecture. We will also explore the feasibility and limitations of this architecture in different scenarios.
Updated: 05/18/2005
|
|
|
In the 1990s, enterprises discovered that storage was best treated as infrastructure, and network attached storage went from being a radical idea to a mainstream solution in the course of only a few years. Today, network attached processing—consolidating middle-tier server sprawl into a small pool of compute appliances—is poised to deliver similar management and consolidation benefits to J2EE deployments, which can reduce the cost and complexity associated with developing, deploying, managing, and provisioning distributed J2EE applications.
Updated: 05/18/2005
|
|
|
In this article, we will discuss: CMP 2.0: What has changed? The Inventory EJB application. Developing a CMP bean. Migrating the bean to use BMP.
Updated: 05/18/2005
|
|
|
Over the last six months, a number of standards have begun to emerge in the areas of Web services' lifecycles, security measures, collaborations, and transactions. JSRs have emerged to begin the process of defining, in a standard way, the different aspects of how Web services might be supported in a J2EE-compliant application server.
Updated: 05/18/2005
|
|
|
Caching is one of the tried-and-true techniques for improving the efficiency of an application. That's especially true in an enterprise environment, where the range of users can include remote clients accessing the app in a variety of modes, and in integrated apps where several departments are constantly grabbing at the same data.
Updated: 05/18/2005
|
|
|
This week on ONJava.com, BEA Systems' Al Saganich describes one of the latest emerging Java Web services specifications, JSR 109. This Java Specification Request in the Java Community process (JCP) effectively defines how a J2EE application server extends and natively supports standard Web services specifications and APIs through access, deployment, and management. Al explains JSR 109 in the context of the client and server programming models, and examines how JSR 109 deploys Web services in these models.
Updated: 05/18/2005
|
|
|
The Java 2 Enterprise Edition (J2EE) is a specification for an enterprise framework that has been widely adopted for its multi-platform, Internet-ready, thin-client architecture. J2EE provides a comprehensive specification for enterprise-wide Java technologies, as well as server-side and client-side support for developing multi-tier enterprise applications.
Updated: 05/18/2005
|
|
|
This article is targeted toward J2EE developers. It requires some familiarity with Macromedia Flash and its ActionScript scripting language. Flash developers building interfaces to J2EE applications will also benefit from the information provided here.
Updated: 05/18/2005
|
|
|
This article is excerpted from Chapter 7, \"Creating a Shared Database,\" of Microsoft .NET and J2EE Interoperability Toolkit [Microsoft Press, 2003, ISBN: 0735619220]. It has been edited for length and format to fit the magazine. You can achieve interoperability between the Microsoft .NET Framework and Java 2 Enterprise Edition (J2EE) simply and effectively with a shared database. Database connectivity lies at the core of both .NET and J2EE, allowing you to exploit the data access drivers available for each and whip out applications that share fields, records, and tables among both platforms.
Updated: 05/18/2005
|
|
|
J2EE Listings
|
|
Total:
100 | Displaying: 11 - 20 | Pages: << 1 2 3 4 5 6 7 8 9 10 >> |
|
|
