WebProNews

Using J2EE to Drive J2ME Applications

Wireless technology is evolving at a rapid pace. There is a lot of talk about mobile and wireless computing and there is also a fair amount of hype. However, the one thing that is conspicuously absent from much of these discussions on mobile and wireless computing is a discussion on what these devices are connecting to. The fact is, most of the value, in terms of content and capabilities of the device, is a result of interacting with a server of some type. This is true whether we are talking about microbrowsers such as WAP and iMode, J2ME clients, or short message service (SMS) and email. Behind the scenes these devices are interacting with services that reside somewhere on a network. These services handle much of the complex details of the features offered by wireless devices. Although there are complexities that the mobile device must deal with, a well-designed wireless architecture delegates as much complexity as possible to the server. This is desirable because servers have more processing capabilities and do not have the power restrictions of mobile devices (i.e., servers don't run on batteries that are worn down by the CPU). This article examines wireless computing from the server's perspective. First, the problems of wireless computing or the public Internet are discussed. Then various models that help address these problems are provided.

The Problem with J2EE

J2EE is a great thing. As a rich collection of technologies to support the development and deployment of server-side business logic written in Java, it is a total marvel. Here at Cape Clear, we believe that while J2EE is great, it isn't the answer to every problem, specifically it is overkill as an infrastructure to deploy Web Services. This article explains why.

How Do J2EE and .NET Measure Up?

As competing platforms for enterprise and ASP applications and Web Services, Sun's Java 2 Platform, Enterprise Edition (J2EE) and Microsoft's .NET are often thrown together in a metaphorical boxing ring: J2EE v .NET? The eager crowd watches to see which one is stronger? Which one will K.O. the other?

Proposing J2EE Based Architecture for Small/Medium Business Applications

We are not able to think of the name of a single enterprise in this modern information technology era that does not have different applications (ranging from simple to vastly complicated) implementing its internal processes and exposing them to their partners (buyers, suppliers, customers, and so forth).

Adding the Finishing Touches On Optimizing J2EE Applications

Code Sample 4: A Page-By-Page Iterator pattern that is returned to the client.

Patterns For Optimizing The Performance Of J2EE Applications

With the proliferation of the J2EE platform as a platform of choice for server-side applications, the need for sharing of developers' experience and availability of reusable designs has become very crucial. In this article, we will get to know some of the reusable designs that can be used for improving the performance of a J2EE application. For the benefit of those who are not familiar with design patterns, a brief description is given at the beginning before delving into the details. For further details on design patterns in general, the reference section at the end of this article will be useful.