.NET
  Home arrow .NET arrow Page 3 - Can J2EE and .NET Provide Cross-Platform I...
ASP Free Forums 
.NET  
ASP  
ASP Code  
ASP.NET  
ASP.NET Code  
BrainDump  
C#  
Code Examples  
Database  
Database Code  
IIS  
Microsoft Access  
MS SQL Server  
Silverlight  
Visual Basic.NET  
Windows Scripting  
Windows Security  
XML  
Mobile Linux 
App Generation ROI 
IBM® developerWorks 
ASP Web Hosting  
ASP.NET Web Hosting 
Windows Web Hosting
 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
.NET

Can J2EE and .NET Provide Cross-Platform Interoperability?
By: Dwight Peltzer
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 2 stars2 stars2 stars2 stars2 stars / 10
    2005-04-13

    Table of Contents:
  • Can J2EE and .NET Provide Cross-Platform Interoperability?
  • J2EE 1.4 Specification
  • Microsoft .NET
  • Third Party Vendors Provide Interoperable Bidirectional Solutions

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Can J2EE and .NET Provide Cross-Platform Interoperability? - Microsoft .NET


    (Page 3 of 4 )

    Microsoft’s .NET platform is component based and sits on top of the Windows operating system. The .NET architecture is Web services-centric and paves the way for interoperability between technologies residing on the .NET platform. The ability to build applications in any programming language targeting the .NET framework is one of the most exciting innovations released by Microsoft in recent years. They designed the Framework to run on any platform, provided the Framework is installed on that system.

    The .NET infrastructure presents a multi-tiered approach to distributed programming and uses SOAP as the primary technology for supporting Web services. The components consist of classes embedded within namespaces such as System.Object, System. Net, System.Windows.Forms, System.Web, and System.XML.

    In a distributed environment, separating .NET’s presentation layer from the middle-tier business logic layer is a good practice. The third tier consists of low-level components for managing services such as database access, connection to legacy applications, and so forth. The .NET Framework uses HTTP as the communications protocol for messaging and exchanging documents via the Internet. This protocol allows any programming language, platform, or middleware to be an interactive participant in cross-platform interoperability. XML serves as the .NET architectural core component and provides the means with which to transmit XML-based SOAP messages.

    The three core components of the Framework consist of the Common Language Runtime (CLR), the Common Type Specification (CTS), and the Common Language Specification (CLS). The CLR performs a wide variety of low-level system tasks, i.e., memory management, error handling, type checking, and security. The CTS defines common data types all programming languages targeting the Framework must conform to in order to receive multilanguage, interoperability support. Remember, a .NET type refers to a collection of classes, interfaces, delegates, and structures supported by the CLR. The CLS sets forth guidelines a .NET-aware compiler must follow before it can receive Framework support. Objects must expose to callers only features common to all .NET hosted languages.

    What is interoperability? Interoperability, considered in the context of Web services, means all functional characteristics of a Web service must remain unchangeable across different operating systems, diverse applications, programming languages, and data business models. Web services, by definition, must be interoperable. Additionally, no service client must be interdependent upon other services.

    More .NET Articles
    More By Dwight Peltzer


     

    .NET ARTICLES

    - Building Applications with Windows Workflow ...
    - Building the Data and Business Layers Using ...
    - The Transformed XML Explorer in MFC
    - List Control and Property Grid with the MFC ...
    - Font, Shell and Masked Edit Controls for MFC
    - Color, Link and Image Editor Controls for M...
    - New Controls for MFC
    - The Windows Ribbon Framework
    - Markup Language for the Ribbon Framework
    - Visually Upgrade Your MFC Project
    - New Features for the Statusbar in MFC
    - Working with the Statusbar in MFC
    - Iron Speed Design v60 Review
    - Binary and XML Serialization
    - Using CrystalReportViewer to Display Crystal...





    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 1 Hosted by Hostway
    For more Enterprise Application Development news, visit eWeek