transportReceiver configuration declarator aggregates 1..n transport.properties +1 Martin--
> From: andreas.veit...@gmail.com > Date: Sun, 19 Jun 2011 17:53:51 +0200 > Subject: Re: Improvements to Axis2 Transports > To: java-dev@axis.apache.org > > +1 from me. I already suggested doing this when the feature was introduced: > > http://markmail.org/thread/zgjo47gsuvggjc7v > > Andreas > > On Mon, Jun 6, 2011 at 09:57, Sadeep Jayasumana <gayansad...@gmail.com> wrote: > > Hi Devs, > > I'm planning to do the following improvement to Axis2 transport framework. > > > > Currently, Axis2 transport framework reads certain configuration information > > related to transport listeners (server core pool size, max pool size, server > > queue length, etc) from a property file found in the classpath. This > > property file is named "<transport-name>.properties" and this name is not > > configurable. Because of this, when there are two or more transport > > listeners with the same name, they cannot have independent configurations. > > (They cannot have different pool sizes, queue lengths etc.) > > After my improvement, user will be able to include all the configuration > > information inside axis2.xml's <transportReceiver> element itself, without > > using <transport-name>.properties file. Therefore, all the transport > > listeners listed in axis2.xml will be able to have independent > > configurations. However, to keep backward compatibility, values will still > > be read from the properties file and values present is axis2.xml's > > <transportReceiver> element will override those read from the properties > > file. > > Does this sound like a good improvement? Your inputs are welcome. > > Thanks, > > -- > > Sadeep Jayasumana > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org > For additional commands, e-mail: java-dev-h...@axis.apache.org >
