ws-sandesha-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Lovett (JIRA)" <>
Subject [jira] Updated: (SANDESHA2-15) Enable Sandesha2 to send unreliable messages
Date Wed, 12 Jul 2006 08:36:30 GMT
     [ ]

Matt Lovett updated SANDESHA2-15:

    Attachment: NOTICE.txt

Sorry folks, but I just noticed that the Sandesha distribution doesn't contain a NOTICE file
to allow us to record the IBM copyright material that we are contributing. The Axis2 distribution
put the NOTICE file in as an alternative to scattering copyright notices throughout the code.

Please add this NOTICE.txt to the top of the sandesha2 java tree. Let me know if we should
be discussing this some more!

Thanks, Matt

> Enable Sandesha2 to send unreliable messages
> --------------------------------------------
>          Key: SANDESHA2-15
>          URL:
>      Project: Apache Sandesha2
>         Type: New Feature

>     Reporter: Matt Lovett
>     Priority: Minor
>  Attachments: NOTICE.txt, Unreliable.patch
> Some clients will want to send a mix of reliable and unrealiable messages. Ideally, they
should be able to do that by using a single axis2 configuration (with Sandesha engaged), by
passing parameters into the invocation. I propose adding a new "UNRELIABLE_MESSAGE" property
into SandeshaClientConstants, so that applications can disable RM for a given invocation.
I'll put in some new unit tests that make sure that unreliable messages work for both 1 and
2-way messaging.
> An alternative implementation is to set the internal APPLICATION_PROCESSING_DONE property
onto the message context, but that seems like messing with Sandesha internals when a client
constant would be more appropriate.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message