Java .NET Interop Special Report

Java/.NET Interoperability via Shared Databases and Enterprise Messaging

un’s Java 2 Enterprise Edition and Microsoft’s .NET Framework represent the two undisputed titans of n-tier, enterprise software platforms. Although most IT departments will standardize on one of these platforms as their exclusive dance partner, it’s often necessary and sometimes even desirable to tango with both platforms. Other articles in

Hosting .NET Controls in Java

any organizations have applications already written in Java; but applications often aren’t static?they need constant attention and modifications to remain productive. When it’s time to upgrade, rather than rewriting the base functionality underlying these applications, it’s often more feasible to extend them by taking advantage of the rich new user

Microsoft .NET and Java: Achieving Interoperability

s we head into 2004, for me it’s a time to reflect how far our industry has evolved over the past twelve months, and the pace at which new technologies and ideas are introduced. During the past few years, organizations recognized both the need and the benefits of the .NET

Calling Java Classes Directly from .NET

t’s a fact that most production environments now use a mixture of both Java and .NET, despite all the partisan disputes over which side should “win.” To be prudently responsible in the face of this business reality, it is imperative that developers get both sides to work together. Interoperability is

Connecting CORBA to .NET

ORBA, the acronym for Common Object Request Broker Architecture, is a widely used communications model for building distributed (multi-tier) applications that connect both cross-platform and cross-language clients to server-based services. Like J2EE, it’s not easy to connect CORBA to the .NET world, where ASP.NET Web services and .NET Remoting are