synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ruwan Linton <>
Subject Re: startup order - correct place to start transport listeners
Date Mon, 30 Mar 2009 22:17:50 GMT

On Sun, Mar 29, 2009 at 3:05 PM, Hubert, Eric <>wrote:

> Hi all,
> hmm, I quickly tried to change the order and it seems to work without
> problems.
> > This is a side effect of the historical and now burned-in dependency on
> > Axis2.. In Synapse, the startup script actually starts Axis2, and then
> > again gets triggered on the startup of Axis2, for the actual Synapse
> > initialization
> Are you sure this is still the case? I noticed Axis2 is calling init() of
> class SynapseInitializationModule.
> But recently the implementation of this method has been completely removed
> (change by Indika on 02.03.2009). Now Synapse seems to initialize more
> independently of Axis2. I could be wrong, as I still don't know the code
> very well.

I just had a look at the changes and realized that this change completely
turned the synapse startup and the architecture upside down. Indika, this
will break the Synapse handler module as well. In other words now synapse is
not initializing as a module of axis2 which I think is wrong and might cause
issues. What was the requirement for this sort of a change?????


> > I do not think this would be possible.. but please feel free to explore
> > any possibilities
> I just tried it out and it looks like working. I would post a patch for
> review, but unfortunately my working file of
> also contains my changes for
> So I would first need to get a clean copy from the repo and merge only
> those changes to provide a useful diff to illustrate the changes.
> Regards,
>    Eric

Ruwan Linton
Senior Software Engineer & Product Manager; WSO2 ESB;
WSO2 Inc.;
email:; cell: +94 77 341 3097

View raw message