axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sanjiva Weerawarana <>
Subject Re: [AXIS2] Proposal for saving the message context
Date Fri, 01 Dec 2006 18:56:48 GMT
On Fri, 2006-12-01 at 10:34 +0000, Matthew Lovett wrote:
> Well, yes, but the current Sandesha approach has it's own issues too. I 
> think that this proposal gives us an alternative, and we should get it 
> into axis2 so that we can see what it enables in Sandesha. There is no 
> problem with having 2 in-memory storage managers for a while... one that 
> forces in the dummy transport and runs the message through 
> 'retransmittable phases', and one that calls the serialise code.
> All we'd need to do is move some of the transport-changing logic from 
> SandeshaUtil into something associated with the storage manager. 
> StorageManager.getUtil().executeAndStore(), etc...
> We could also generalise the unit tests so that we try them with both 
> storage managers. That's no bad thing... for a while I've wanted to be 
> able to run the tests with security turned on, and the same general 
> mechanism would be handy there too.

My concerns have nothing to do with Sandesha- the code that's proposed
for Axis2 doesn't work as advertised because it reconstructs the system
in an inconsistent state. 

Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation;
Founder, Chairman & CEO; WSO2, Inc.;
Director; Open Source Initiative;
Member; Apache Software Foundation;
Visiting Lecturer; University of Moratuwa;

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

View raw message