You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Asankha C. Perera" <as...@wso2.com> on 2006/06/12 12:33:52 UTC
Starting up Axis2 transports
Simply adding a transport receiver to an axis2.xml does not seem to
start it up (e.g. JMS), unless the listener manager is specifically
invoked. I think Axis2 should start up all specified transports at
initialization. If required this could be further controlled by a
parameter which may specify whether all transports should be initialized
in this manner. This feature would be useful to Synapse as well.
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Starting up Axis2 transports
Posted by Dennis Sosnoski <dm...@sosnoski.com>.
+1
- Dennis
Sanjiva Weerawarana wrote:
>
> How about each transport having a flag: autostart=true|false and have it
> default to false?
>
> Same idea but the option is per transport instead of global.
>
> Sanjiva.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: Starting up Axis2 transports
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Tue, 2006-06-13 at 13:43 +0530, Deepal Jayasinghe wrote:
> We had this feature sometimes ago and we had to removed that since there
> were few JIRAs on the list saying why do you start all the transports
> w.o asking. I mean if the axis2.xml has several transport listeners then
> we started all of them whether user wants or not. So I dont like go to
> the same state again.
>
> And like the approach that you mentioned to control this using a
> parameter, so how about the following approach.
> - User can specify any number of transports in axis2.xml
> - but by default we are not going to start any of them
> - if user want to start them then he has to go and change axis2.xml
> (need to add a parameter)
> - If the parameter is there we will start all the transport using
> Listener Manager
How about each transport having a flag: autostart=true|false and have it
default to false?
Same idea but the option is per transport instead of global.
Sanjiva.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: Starting up Axis2 transports
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Tue, 2006-06-13 at 13:43 +0530, Deepal Jayasinghe wrote:
> We had this feature sometimes ago and we had to removed that since there
> were few JIRAs on the list saying why do you start all the transports
> w.o asking. I mean if the axis2.xml has several transport listeners then
> we started all of them whether user wants or not. So I dont like go to
> the same state again.
>
> And like the approach that you mentioned to control this using a
> parameter, so how about the following approach.
> - User can specify any number of transports in axis2.xml
> - but by default we are not going to start any of them
> - if user want to start them then he has to go and change axis2.xml
> (need to add a parameter)
> - If the parameter is there we will start all the transport using
> Listener Manager
How about each transport having a flag: autostart=true|false and have it
default to false?
Same idea but the option is per transport instead of global.
Sanjiva.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Starting up Axis2 transports
Posted by Deepal Jayasinghe <de...@opensource.lk>.
We had this feature sometimes ago and we had to removed that since there
were few JIRAs on the list saying why do you start all the transports
w.o asking. I mean if the axis2.xml has several transport listeners then
we started all of them whether user wants or not. So I dont like go to
the same state again.
And like the approach that you mentioned to control this using a
parameter, so how about the following approach.
- User can specify any number of transports in axis2.xml
- but by default we are not going to start any of them
- if user want to start them then he has to go and change axis2.xml
(need to add a parameter)
- If the parameter is there we will start all the transport using
Listener Manager
comments ..... ?
Asankha C. Perera wrote:
> Simply adding a transport receiver to an axis2.xml does not seem to
> start it up (e.g. JMS), unless the listener manager is specifically
> invoked. I think Axis2 should start up all specified transports at
> initialization. If required this could be further controlled by a
> parameter which may specify whether all transports should be
> initialized in this manner. This feature would be useful to Synapse as
> well.
>
> asankha
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
>
--
Thanks,
Deepal
................................................................
~Future is Open~
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: Starting up Axis2 transports
Posted by Deepal Jayasinghe <de...@opensource.lk>.
We had this feature sometimes ago and we had to removed that since there
were few JIRAs on the list saying why do you start all the transports
w.o asking. I mean if the axis2.xml has several transport listeners then
we started all of them whether user wants or not. So I dont like go to
the same state again.
And like the approach that you mentioned to control this using a
parameter, so how about the following approach.
- User can specify any number of transports in axis2.xml
- but by default we are not going to start any of them
- if user want to start them then he has to go and change axis2.xml
(need to add a parameter)
- If the parameter is there we will start all the transport using
Listener Manager
comments ..... ?
Asankha C. Perera wrote:
> Simply adding a transport receiver to an axis2.xml does not seem to
> start it up (e.g. JMS), unless the listener manager is specifically
> invoked. I think Axis2 should start up all specified transports at
> initialization. If required this could be further controlled by a
> parameter which may specify whether all transports should be
> initialized in this manner. This feature would be useful to Synapse as
> well.
>
> asankha
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
>
--
Thanks,
Deepal
................................................................
~Future is Open~
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org