Hi, On Sun, Jun 29, 2008 at 9:45 PM, Asankha C. Perera <[EMAIL PROTECTED]> 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 > Reading ordinary parameters off the AxisService can be done. Problem is reading the target URI value mentioned in the Synapse config. But as Andreas has mentioned this might make the code Synapse specific. A possible workaround is to introduce a new parameter where the user can specify the target URI to connect to at the start up. However this suffers certain limitations like not being able to connect to more than one session at start up. Thanks Best Regards, Hiranya > > > 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- > Asankha C. Perera > > WSO2 - http://wso2.org > http://esbmagic.blogspot.com > >
