Deepal, With the existing transport deployer, how do you handle the case of a transport sender that can be set up without any configuration, but for which the user might want to set some optional parameters later?
Andreas On Mon, Dec 15, 2008 at 23:02, Deepal Jayasinghe <deep...@gmail.com> wrote: > Not bad, > in fact we have some thing called transport deployer (just like > service deployer) , so if you add the transport deployer into axis2 > and specify the location of transport directory. Then you do not need > to have any of the transport in axis2.xml. Everything is automatic :D > > Deepal > > On Mon, Dec 15, 2008 at 4:56 PM, Andreas Veithen > <andreas.veit...@gmail.com> wrote: >> I think that the default axis2.xml also refers to the TCP sender. BTW, >> wouldn't it be interesting to have a lookup mechanism (like JDK 1.4 >> service providers) that automatically adds the transport senders to >> the Axis configuration? That way the default axis2.xml would work out >> of the box with all transport senders that are available in the >> classpath, at least those that don't need configuration. >> >> Andreas >> >> On Mon, Dec 15, 2008 at 22:30, Glen Daniels <g...@thoughtcraft.com> wrote: >>> Deepal Jayasinghe wrote: >>>> >>>> Well lets add the axis2-transport.jar which has all the transport in it. >>> >>> Hm... Wouldn't it be better to keep the distribution small by default now >>> that it's so easy to just drop transport jars in? I think we should just >>> include http and local baked in, and then make it dead easy for people to >>> download and add the others. >>> >>> Optionally we could actually start doing what we talked about at the very >>> beginning of Axis2, releasing profiled builds - embedded, basic, complete, >>> etc... >>> >>> --Glen >>> >> >
