On Tue, Mar 4, 2008 at 6:19 PM, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
> ant elder wrote: > > Ok thanks. The <binding.ws> element is also extensible so this axis2 > config > > could be added as extra attributes or elements there couldn't it, eg < > > binding.ws timeOut="300000" />? Which seems simpler if allowed so why is > the > > policySet approach better? > > > > <binding.ws timeout="300000" connections="10"> will require you to go > open your application jar and change the .composite provided by the > application developer to adjust the timeout or number of connections. > > Policies allow you to configure and adjust qualities of service like > timeouts, connection pools etc. without touching the logical composition. > -- > Jean-Sebastien > > Ok that makes sense. But how does this compare to say the JMS binding which does support configuring QOS related things (priority, time to live etc) via binding attributes? ...ant
