Of the various interoperability solutions presented in this special report overview, which do you see as the most important, long term? Web services or the various methods of binary interop? Do you think this is a comprehensive list or are there other ways to get the two technologies to work together? Do you think interoperability is a desirable goal, or do you think organizations should choose one technology and then rewrite as needed until they no longer need interoperability internally? Let us know in the Java or .NET discussion forums.
Microsoft .NET and Java: Achieving Interoperability
Although Web services are the technology most people immediately assume will solve their interoperability problems, one size does not fit all. But regardless of your needs or expectations, an interoperability solution probably exists to fulfill them. Read this quick overview to begin exploring the various methods for achieving interoperability between Java and .NET.
by Simon Guest
January 21, 2004
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 and Java platforms, recognized that each has specific costs and benefits, and built applications that run on both. Not surprisingly, given that mix of platforms, they're now finding an increasing need for interoperability, and are starting to consider the best approach for achieving that interoperability.
Interoperability through Web services has received the greatest amount of attention, and in this last year we've seen many advances in Web services stacks from both Microsoft and many Java vendors. However, Web services are not the only option to create an interoperability solution. Other options exist that provide interoperability through means other than Web services. These include numerous third party solutions, asynchronous interoperability using databases, and the use of message queues to relay messages between the two.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
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 and Java platforms, recognized that each has specific costs and benefits, and built applications that run on both. Not surprisingly, given that mix of platforms, they're now finding an increasing need for interoperability, and are starting to consider the best approach for achieving that interoperability.
