Many enterprise projects use .NET based technology on the client side, where richness and performance are paramount considerations. This is then teamed up with a proven, stable, mature platform for server based enterprise applications, J2EE. While many enterprise projects have realized the power of this dynamite combination, several questions related to the interoperability considerations of using .NET with J2EE have gone unanswered. In this article, Binil Christudas attempts to shed light on this important, yet sparsely documented, area of interoperability considerations and some of the solutions available to work hassle-free with .NET and J2EE . The article converges at a point, and rightly so, to propose Web Services as a technology for attaining client side interoperability, and in that attempt addresses two important approaches: Top-Down and Bottom-Up. As proof of the proposed technology, practical demonstration of the two approaches, and the successful implementation of a solution, the author showcases a sample architecture based on BEA Weblogic Server and .NET C# client. Cruise along and pick up some nuggets for your next project that uses this potent combination
A Look into the Architecture and Development Process using the Magic Template
The first part of this series introduced us to the EJOSA magic template - a solution for J2EE beginners who wish to overcome the complexity of J2EE application development by using Open Source Software (OSS). In the second part of this series, we will move further into the workings of EJOSA Template and look at the specification directory, which is the most important part of EJOSA Template; the business layer, where you implement the specification with available Java technologies; the presentation layer that represents the view of the business logics; and the road ahead for the EJOSA Template.
Optimizing Your Applications with Enerjy Performance Profiler
This article is aimed at developers and architects who are currently developing Java applications, or have developed applications, and want to optimize them for speed or throughput. The author explains why profiling techniques should be adopted and focuses on the use of Enerjy Performance Profiler to aid in this methodology.
From its conception to its current invocation, one of the most favourable merits of the Java language (currently Java 5) is automatic memory management. Unlike other languages, developers no longer have to worry about the many mistakes that can occur from the more traditional languages, for example, allocating memory or forgetting to free dynamically allocated memory. The JVM will generally free up memory when it reaches a certain limit or when it needs more memory to continue execution of an application. Due to the mechanics of the garbage collector however, once an object is de-referenced there is no guarantee that the object will be cleaned up.
The Enterprise Java Open Source Architecture (EJOSA) Template was built to help computer science students, at the University of Munster, develop J2EE projects with a low learning curve. With little to no experience in J2EE, and a modest experience in Java, students were able to use the EJOSA template to create robust and production-ready J2EE projects. In the first part of this article, EJOSA architect Lofi Dewanto takes a close look at this magic template -- Enhydra (Web container), JOnAS (EJB container) and HypersonicSQL (data container for development) or Firebird DBMS (data container for production).
It is a fact of life -- developers like to write code in different styles. Show us code written by ten different developers and we can show you ten different coding styles. So why should we try to develop and enforce coding standards?
The ABAP-speaking developer community in Walldorf is increasingly speaking Java. This process of evolution began when SAP acquired InQMy along with its ready-to-market J2EE technology, and Hasso Plattner (the co-chairman of SAP) announced that ABAP and Java would rank equally in application development at SAP.
SAP's New Model-Driven Programming Model Revolutionizes the Development of User Interfaces
Highway 1 in California - also know as the Pacific Coast Highway - winds in narrow hairpin curves through deep gorges. Anyone wanting to get to Los Angeles from San Francisco quickly, however, takes Highway 101, which cuts a straight line through the countryside. One could describe the road from ABAP/Dynpro to Web Dynpro in a similar way. The ABAP/Dynpro development model, created in the nineties, played a significant part in the development of ABAP-based SAP applications. In the meantime, powerful standards like Java/J2EE and Web Services were developed, which were driven and supported by SAP. Since Hasso Plattner's announcement that the SAP application server will support J2EE as well as ABAP, a new generation of SAP development tools has emerged. These tools support a new, powerful concept for building Web-based user interfaces: Web Dynpro for Java.
