Correct mar processing so properties files are added to the Sandesha mar |
|
More...
|
almost 18 years ago
|
[no comment] |
|
More...
|
almost 18 years ago
|
Fixed test cases - to work from within IDEs |
|
More...
|
almost 18 years ago
|
Skip Sandesha processing if RM is not enabled for a Service. |
|
More...
|
almost 18 years ago
|
Avoid deadlock between Invoker and InvokerWorker when dealing with a 2-way message. Deadlock is caused by RMDBean and InvokerBean taken in different orders. |
|
More...
|
almost 18 years ago
|
Updated the pom files |
|
More...
|
almost 18 years ago
|
See http://issues.apache.org/jira/browse/SANDESHA2-87 |
|
More...
|
almost 18 years ago
|
Optimized the maven scripts |
|
More...
|
almost 18 years ago
|
Fixed test cases. |
|
More...
|
almost 18 years ago
|
patch from sumedha - Sandesha2 86 |
|
More...
|
almost 18 years ago
|
More corrections from Sumedha |
|
More...
|
almost 18 years ago
|
More changes for the maven2 build - Added the interop module |
|
More...
|
almost 18 years ago
|
Updated pom.xml |
|
More...
|
almost 18 years ago
|
More changes for Sandesha2 86 |
|
More...
|
almost 18 years ago
|
patch for - Sandesha2 86 |
|
More...
|
almost 18 years ago
|
Applied the patch from Sumedha on the maven2 build - Sandesha2 86 |
|
More...
|
almost 18 years ago
|
Folder structure for the maven2 build |
|
More...
|
almost 18 years ago
|
Sorry, that was a mistake :-) |
|
More...
|
almost 18 years ago
|
Some changes to the RMScenarioTest - Omited the checking of the termination of the response message in WSRM 1.0 sync InOut case. Since we terminate with the SandeshaClient.terminateSequence method, we send the Empty Body Last Message but still the server has not corrected to respond with a LastMessage. |
|
More...
|
almost 18 years ago
|
Corrected the SandeshaClient.terminateSequence method. - This was not sending an ampty LastMessage in the WSRM 1.0 case, but this is wrong according to the protocol. Several other bug fixes. |
|
More...
|
almost 18 years ago
|
Added the dependancy commons-fileupload. Some changes to dependency versions. |
|
More...
|
almost 18 years ago
|
Updated the axis2.xml files |
|
More...
|
almost 18 years ago
|
A bug fix |
|
More...
|
almost 18 years ago
|
Improved the target resolver to set "USE_ASYNC" to false when Sandesha2 is not engaged. |
|
More...
|
almost 18 years ago
|
See http://issues.apache.org/jira/browse/SANDESHA2-85 |
|
More...
|
almost 18 years ago
|
Enable the CSR Fault test. Move the RM Fault processing to the SandeshaGlobalInHandler which fixes the action not found error for RM1.0 Fault messages |
|
More...
|
almost 18 years ago
|
Check for AxisOperation in SandeshaModule.engageNotify as well as AxisService when deciding if it is an out in operation for RM Auto offering |
|
More...
|
almost 18 years ago
|
Commit transaction after processing each part of the message inside the SandeshaInHandler. This fixes both a deadlock with the SenderWorker with ordering of RMS/RMDBeans |
|
More...
|
almost 18 years ago
|
See http://issues.apache.org/jira/browse/SANDESHA2-84 |
|
More...
|
almost 18 years ago
|
SenderBean not locked when updating the next retransmission time. InMemorySenderBeanMgr can return a SenderBean which is not eligible for sending |
|
More...
|
almost 18 years ago
|