> Transports are configured using parameters added to the corresponding > <transportReceiver> and <transportSender> elements. If the transport > is simply added to the classpath, these elements are placed in > axis2.xml, while in the case of deployment using the transport > deployer, they must be placed in the META-INF/transport.xml file > inside the archive. I guess that you don't expect users to unzip the > transport archive, change transport.xml, rezip it and redeploy it, so > I must have missed something... > Nope I did not mean that. What I was referring here is that if the transport need some kind of parameter, then we can provide them using axis2.xml or runtime.
Anyway I understand what you mean, I think the deployer is more useful custom transport. For the default transport we may have to use axis2.xml as it is. I think same argument is valid more module like sandesha and rampart, if someone want to configure them how do they do ? Deepal > Andreas > > On Mon, Dec 15, 2008 at 23:51, Deepal Jayasinghe <[email protected]> wrote: > >> well it is same as how do you set up services I guess. One thing you >> could do is you can provide parameters though axis2.xml. Or you can >> change them at runtime >> - get the transport sender >> - get the transport description >> - add the configuration >> >> Deepal >> >> On Mon, Dec 15, 2008 at 5:38 PM, Andreas Veithen >> <[email protected]> wrote: >> >>> 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 <[email protected]> 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 >>>> <[email protected]> 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 <[email protected]> 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 >>>>>> >>>>>> > > -- Thank you! http://blogs.deepal.org
