I committed this change, was unable to test the WAR distribution. Even though it has to work if some one can test this and let me know if there is any issue, that would be very helpful.
Apart form that, since this is a fundamental change please let me know if there is any issue... I ran most of the samples (but not all) including security once which triggers the SynapseMustUnderstandHandler and so on, all of which seems to be working fine. Unregistering part of these handlers is also added to the appropriate stopping flow... So, Synapse is no more a module of axis2. Thanks, Ruwan On Fri, Apr 10, 2009 at 6:47 PM, Hubert, Eric <eric.hub...@foxmobile.com>wrote: > If you look at the way synapse operates, even though it seems like a > module of axis2 it is really not, it just uses the axis2 handler > architecture to leverage the other axis2 features while getting the message > dispatched into synapse. So I propose to drop the module and > programaticaly register theses handler after properly initializing the > Synapse environment. > > WDYT? > +1 – I think your explanation gets to the heart of it. > -- Ruwan Linton Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com
