A generics-based technology for facilitating the interchange of objects between Java 5.0 and .NET 2.0 applications.
Tutorial Details:
What is IBM Message Service Clients Extensions for Generic Programming?
This extension to Java™ Message Service (JMS) and IBM Message Service Clients for .NET (XMS) exploits "generics," a type-safe feature of Java 5.0 and Microsoft .NET Framework 2.0, in order to provide a standards-based messaging framework for object interchange. This technology provides several benefits:
* It is interoperable: One can send and receive objects between Java and .NET environments and easily interpret them.
* It is type-safe for both the sender and the receiver.
* It is general: One can send or receive objects that do not implement the Java.IO.Serializable interface.
* It supports the sending and receiving of partial objects.
* It provides type flexibility: The receiver need not treat the object in the message as the same type it was on the sender's end.
How does it work?
In order to send an object in a message, the user must provide an encoder object that converts objects of the type being sent to XML conforming to a user-supplied schema. When an object is sent, the schema URI and the encoded XML form of the object are placed into a JMS TextMessage and sent to the specified destination.
In order to receive an object from a message, the user must provide a decoder object that converts XML conforming to a user-supplied schema into an object of the desired type. Messages that match the schema are selected from the specified destination and decoded with the decoder before being returned to the user's program.
Read
Tutorial at: Click here to view the tutorial
Rate Tutorial: Safely Interchange Objects between Java and .Net apps
View Tutorial: Safely Interchange Objects between Java and .Net apps
Related
Tutorials:
 Accelerate your Java apps! - JavaWorld - September 1998
Accelerate your Java apps! - JavaWorld - September 1998
|
Java Tip 42: Write
Java apps that work with
proxy-based firewalls - JavaWorld - December 1997
Java Tip 42: Write
Java apps that work with
proxy-based firewalls - JavaWorld - December 1997
|
Understanding Java Card 2.0 - JavaWorld March 1998
Understanding Java Card 2.0 - JavaWorld March 1998
|
Scripting power
saves the day
for your Java
apps
Scripting power
saves the day
for your Java
apps
|
Smart object-management saves the
day - JavaWorld November 1999
Smart object-management saves the
day - JavaWorld November 1999
|
Java Tip 84: Customize
scoping with object keys - JavaWorld
Java Tip 84: Customize
scoping with object keys - JavaWorld
|
Make a sweep with
clean beans -
JavaWorld
November 1999
Make a sweep with
clean beans -
JavaWorld
November 1999
|
C# : A language alternative or just J--? (part1)
C# : A language alternative or just J--? (part1)
|
Avoid synchronization
deadlocks
Avoid synchronization
deadlocks
|
Use Web services
to integrate Web applications with
EISs
Use Web services
to integrate Web applications with
EISs
|
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
|
Java is here to stay (JavaWorld / January 2000 / by John Rommel)
Java is here to stay (JavaWorld / January 2000 / by John Rommel)
|
Let the mobile
games begin, Part 2
Let the mobile
games begin, Part 2
|
Make the Java-Oracle9i
connection
Make the Java-Oracle9i
connection
|
Call on extensible RMI
Call on extensible RMI
|
elegant turnaround
elegant turnaround
|
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
|
Simple Object Persistence with the db4o Object Database
Simple Object Persistence with the db4o Object Database. db4o has been chosen for applications in embedded systems in which zero administration, reliability, and low footprint are critical features. In Germany, BMW Car IT, for example, uses it in an embed
|
|
|
|
