Extended messaging - data mapping
A message bean can use data mapping to map between a JMS message and data
as arguments:
- With data mapping, the target method of a receiver bean for an anonymous
invocation receives the contents of an asynchronous message as arguments.
The extended messaging service parses the JMS message and maps from the JMS
message to the method arguments. Similarly, to send a message, an application
invokes a method on a sender bean with appropriate arguments. The extended
messaging service packs appropriate arguments into a JMS message then sends
the asynchronous request.
- Without data mapping, the target method of a receiver bean for an anonymous
invocation receives a JMS message; no data mapping is performed by extended
messaging. Similarly, to send a message, an application invokes a method of
a sender bean with a JMS message.
If a developer selects data mapping when creating a sender or receiver
bean, extended messaging uses the parameter properties specified on the sender
or receiver bean method signatures to perform the data mapping.

Extended messaging - receiving messages
Extended messaging - sending messages
Extended messaging - handling late responses
Extended messaging - application usage scenarios
Searchable topic ID:
cmc_ovw03
Last updated: Jun 21, 2007 8:07:48 PM CDT
WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/cmm/concepts/cmc_ovw03.html