Here is my proposal, We introduce a start method to the SynapseController so that we can init the Axis2 environment in the init method of the controller and then initialize the Synapse environment after creating the SynapseConfiguration and call this introducing start method.
init method of the controller initializes the listener manager and add all the listeners parsing true to not to start the listeners upon adding them to the listener manager. In the start method we start the listener manager which intern will start all the listeners. Further, post starting tasks like starting the Tasks and so on has to be handled with a different call after the start call. We may come up with a different interface for these or introduce a method to the ManagedLifecycle interface called start, apart from the init and destroy methods so that the start method will be called after starting the listener manager, from the ServerManager class. This resolves the issue... WDYT? Thanks, Ruwan On Fri, Apr 3, 2009 at 3:19 PM, Hubert, Eric <eric.hub...@foxmobile.com>wrote: > I am trying to come up with a proposal to implement this. When we do a > considerable change, it is better to discuss things before commiting to > implement that even though we are operating on CTR model. > > > > Ruwan, I fully agree. While reading the dev list I noticed quite often that > the final result of a discussed solution profited a lot from valuable input > of other developers. For me this is simply a combined (team) strength which > could be used even more actively. > > > > Regards, > > Eric > > > -- 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
