axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dasarath Weeratunge <dasarathweeratu...@yahoo.com>
Subject [Axis2] messaging based core discussion summary
Date Thu, 31 Mar 2005 11:55:36 GMT
At the axis2 summit, the messaging based core
discussion ultimately boiled down to renaming several
entities.

People agreed to have a MessageSender with
send(MessageContext mc) method and a MessageReceiver
with a receive(MessageContext mc) method. One
important difference between the MessageSender and the
MessageReceiver is that the MessageSender encapsulates
the handler chain but not the MessageReceiver.
MessageSender simply replaces the Sender that was in
the earlier architecture and MessageReceiver simply
replaces both the Receiver and the provider. The code
sharing concerns that lead to the separation of
Provide and Receiver in the earlier summit was settled
by agreeing on having all custom MessageReceivers
extend built in standard Receiver.

Another important conclusion was to restrict the Call
API for handling only the request response pattern.
For any other interaction patterns the users will need
to use the MessageSender + MessageReceiver API.

The AxisEngine shall continue to retain the
send(MessageContext mc), receive(MessageContext mc)
methods. The MessageSender.send(MessageContext mc)
will call AxisEngine.send(mc) to perform the actual
sending.

In addition sender, receiver terminology will also be
used in the transports. The new inflow and outflow
shown below:

Outflow

MessageSender.send -> AxisEngine.send ->
TransportSender.send


Inflow

TransportReceiver.receive -> AxisEngine.receive ->
MessageReceiver.receive

--Dasarath


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Mime
View raw message