see TransportSenderLocator class ... right now the options are hardcoded. We need the transport to load via the server.xml but as we do not discuss it much I keep it as it is for M1
To write a new transport see AbstractTransportSender.java and HTTPTransportSender.java and write a new transport sender and add it by adding a entry to TransportSenderLocator.java Thanks Srinath On Wed, 23 Feb 2005 09:24:21 -0500, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Jaya, > > +1 to write a CommonsHTTPTransportSender for Axis2. Do you want to > take a stab at it? > > thanks, > dims > > > On Wed, 23 Feb 2005 19:51:11 +0530, jayachandra <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > Is there a way to use a different transport than HTTPTransportSender > > in Axis2, say something like commonsHTTPSender or axis1.x version's > > HTTPSender. Because they seem to be more robust than this and also at > > my end when I tried the interop testing (both from command line and as > > well using the interop.jsp webinterface), except for localhost's > > interop-doclit service for other endpoint URLs mentioned in the > > http://www.whitemesa.net/r3/interop3.html, I was unable to succeed. I > > seem to fail miserably with java.net.SocketException everytime. > > > > I've looked into the syntax structure of service.xml in the > > Axis2ArchitectureGuide.html, but there is no mention about transport. > > Should it be given as a parameter? > > > > Thank you, > > Jayachandra > > -- > > -- Jaya > > > > -- > Davanum Srinivas - http://webservices.apache.org/~dims/ >
