Java and .Net interoperability using CORBA
A recently released product takes the pain out of implementing object-level calls between Java and .Net
While the need for interoperability between Java and .Net has become a common problem in larger organ
Tutorial Details:
The Hello CORBA application
In this article, you learn how to write a simple CORBA application of the "Hello World" type. The client calls the server and passes a parameter named sendMsg, containing the value Spring. The server writes the string "Hello " + sendMsg to the console and returns the value "Good Bye Winter" to the client. The client writes the returned string to the console as well.
The server application is based on the hello sample that ships with the MiddCor trial version. You can quickly get the server up and running by modifying the sample source files.
Write the IDL
The IDL (interface definition language) defines the namespace, class names, and method signatures for the exposed calling interfaces.
Its constructs resemble Java interfaces. The sample application's IDL is rather simple:
module HelloCorba
{
interface Greetings
{
string hello( in string sendMsg);
};
};
The module section defines the namespace. We will publish the namespace in the IOR file (interoperable object reference), so that the client can use it to find the referenced service. In the C# server code, you embed your class implementation in a namespace section.
interface is the name of the servant (i.e., server) object. We will see that for the actual implementation, the suffix Impl is appended, a widely used convention.
The class Greetings has one exposed method, hello(), which expects a string parameter and returns also a string. Note that the example uses only the IDL data type string.
Save the file in a directory of your choice and call it hello.idl.
Read
Tutorial at: Click here to view the tutorial
Rate Tutorial: Java and .Net interoperability using CORBA
View Tutorial: Java and .Net interoperability using CORBA
Related
Tutorials:
 The state of Java middleware, Part II: Enterprise JavaBeans - JavaWorld - April
1999
The state of Java middleware, Part II: Enterprise JavaBeans - JavaWorld - April
1999
|
A beginner's guide to Enterprise JavaBeans - JavaWorld - October 1998
A beginner's guide to Enterprise JavaBeans - JavaWorld - October 1998
|
The state of Java application middleware,
Part 1 - JavaWorld March 1999
The state of Java application middleware,
Part 1 - JavaWorld March 1999
|
RMI over IIOP -
JavaWorld
December 1999
RMI over IIOP -
JavaWorld
December 1999
|
Brewing entity
Enterprise JavaBeans - JavaWorld September
2000
Brewing entity
Enterprise JavaBeans - JavaWorld September
2000
|
C# : A language alternative or just J--? (part1)
C# : A language alternative or just J--? (part1)
|
Clean up your wire protocol with SOAP, Part 1 - JavaWorld March 2001
Clean up your wire protocol with SOAP, Part 1 - JavaWorld March 2001
|
Integrate EJBs with CORBA
Integrate EJBs with CORBA
|
Is WSDL the
indispensable API?
Is WSDL the
indispensable API?
|
Rumble in the
jungle: J2EE versus .Net, Part
2
Rumble in the
jungle: J2EE versus .Net, Part
2
|
J2SE 1.4
breathes new life into the CORBA community, Part
1
J2SE 1.4
breathes new life into the CORBA community, Part
1
|
J2SE 1.4
breathes new life into the CORBA community, Part
2
J2SE 1.4
breathes new life into the CORBA community, Part
2
|
J2SE 1.4
breathes new life into the CORBA community, Part
4
J2SE 1.4
breathes new life into the CORBA community, Part
4
|
J2EE 1.4 eases Web service development
J2EE 1.4 eases Web service development
|
Welcome to the WfMOpen project
WfMOpen is a J2EE based implementation of a workflow facility (workflow engine) as proposed by the Workflow Management Coalition (WfMC) and the Object Management Group (OMG).
|
Java and .Net interoperability using CORBA
Java and .Net interoperability using CORBA
A recently released product takes the pain out of implementing object-level calls between Java and .Net
While the need for interoperability between Java and .Net has become a common problem in larger organ
|
Light-Weight Visual Components Library for different platform: SWT, J2SE, J2ME, .NET
Light-Weight Visual Components Library for different platform: SWT, J2SE, J2ME, .NET
|
Java RMI Tutorial
This is a brief introduction to Java Remote Method Invocation (RMI). Java RMI is a mechanism that allows one to invoke a method on an object that exists in another address space.The other address space could be on the same machine or a different one. The
|
Interoperability with Patterns and Strategies for Document-Based Web Services
In Part 2 of this article, we demonstrate interoperability for document-driven web services with Microsoft .NET (C#) using strategies discussed in Part 1.
|
DB Visual Architect for Eclipse
DB Visual Architect for Eclipse (DBVA-EC) is a full featured Object Relational Mapping (ORM) plugin for Eclipse that provides the industry\'s best round-trip code engineering support with Java.
|
|
|
|
