You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Ruwan Linton <ru...@gmail.com> on 2009/04/08 20:05:19 UTC
Registering the handlers programatically
Folks,
I just realized that because of the change in the Synapse startup, now we
are having an issue with the Synapse handlers being registered via the axis2
module. Here is the issue;
We now initializes Synapse and starts it through a different call than the
Module#init() method, which seems to be correct because for synapse to start
we need a properly initialized axis2 environment. Even though this is now
fixed, this actually doesn't fix the proper start order of the Synapse,
because now the handlers to intercept the messages and bring them into the
Synapse Environment is still registered in the axis2 handler chain before
the Synapse environment gets initialized. Even though this doesn't causes an
issue for the default setup (listeners will not be open till Synapse starts
properly) we are going to have issues when you try to start Synapse on an
already initialized axis2 environment.
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?
Thanks,
Ruwan
--
Ruwan Linton
Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com
Re: Registering the handlers programatically
Posted by Ruwan Linton <ru...@gmail.com>.
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 <Er...@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: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com
RE: Registering the handlers programatically
Posted by "Hubert, Eric" <Er...@foxmobile.com>.
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.
Re: Registering the handlers programatically
Posted by Andreas Veithen <an...@gmail.com>.
+1
Sounds good.
Andreas
On Wed, Apr 8, 2009 at 20:05, Ruwan Linton <ru...@gmail.com> wrote:
> Folks,
>
> I just realized that because of the change in the Synapse startup, now we
> are having an issue with the Synapse handlers being registered via the axis2
> module. Here is the issue;
>
> We now initializes Synapse and starts it through a different call than the
> Module#init() method, which seems to be correct because for synapse to start
> we need a properly initialized axis2 environment. Even though this is now
> fixed, this actually doesn't fix the proper start order of the Synapse,
> because now the handlers to intercept the messages and bring them into the
> Synapse Environment is still registered in the axis2 handler chain before
> the Synapse environment gets initialized. Even though this doesn't causes an
> issue for the default setup (listeners will not be open till Synapse starts
> properly) we are going to have issues when you try to start Synapse on an
> already initialized axis2 environment.
>
> 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?
>
> Thanks,
> Ruwan
>
> --
> Ruwan Linton
> Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org