synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera" <>
Subject Re: Reading Target Address Parameter at Transport Level
Date Sun, 29 Jun 2008 17:10:32 GMT

Andreas Veithen wrote:
> As far as I understand the requirement is as follows: When the 
> transport sender transmits the first message to a given endpoint, it 
> needs to create a session with the endpoint. This operation is 
> expensive and causes a delay if the message is received and forwarded 
> by a proxy service. Since Synapse knows about the endpoints it will 
> connect to, the idea is to create these sessions in advance (at 
> startup) so that the proxy service will forward the first message 
> without delay. However the transports can't get access to the required 
> information because it is managed by Synapse specific classes.
If the above description from Andreas holds, I do not think the 
transport sender could pre-establish sessions as per requirements of 
different services. However, check how the JMS sender uses connection 
pools (if defined), which are initialized at the startup.

> On 29 juin 08, at 18:15, Asankha C. Perera wrote:
>> Hiranya
>> The description of the issue does not make me understand much about 
>> the underlying problem, but some transports like JMS, Mail, VFS etc, 
>> will only poll/connect on behalf of services that registers with 
>> them. So, you can get the service.xml parameters (or Proxy service 
>> parameters), from the AxisService, and there you could define what 
>> you want for the transport. This will not make the transport Synapse 
>> specific, as Axis2 can work too
>> hope this helps
>> asankha
>> Andreas Veithen wrote:
>>> Transports should not contain any code specific to Synapse. Maybe 
>>> you can achieve your goal by creating a org.apache.synapse.Startup 
>>> implementation?
>>> Andreas
>>> On 29 juin 08, at 16:47, Hiranya Jayathilaka wrote:
>>>> Hi Devs,
>>>> Can we access the information like target address endpoints, we 
>>>> normally put in the synapse configuration, at the transport level 
>>>> (at a transport listener to be precise)? I want to read the target 
>>>> address of a proxy service at the transport level. This is required 
>>>> to resolve SYNAPSE-380. I have access to the configuration context 
>>>> and the AxisService object of the proxy service.
>>>> Thanks in advance
>>>> Best Regards,
>>>> Hiranya Jayathilaka
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
>>> For additional commands, e-mail:
>> -- 
>> Asankha C. Perera
>> WSO2 -

Asankha C. Perera

WSO2 -

View raw message