Yes, 2.1 was buggy in a way that timeout setting was not recognized in all container flavors. Due to the numerous spots on where things can time out we decided to have a single timeout indicator and set most of it with this one in 2.2. I don't really know how the hardcoded setting slipped into 2.1 though.
On Mon, Aug 29, 2011 at 9:56 AM, Sanjeeb Sahoo <[email protected]> wrote: > In http://team.ops4j.org/browse/PAXEXAM-222 , we added some code to avoid > hardcoding timeout values, but it seems that code has been replaced some new > code in 2.1.0, but in the process we have again hardcoded the timeout value. > Can anyone tell me how I can specify timeout for exam2.1.0? Or, is upgrading > 2.2.0 which has new api to set timeout value my only option? > > Thanks, > Sahoo > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > > -- Toni Menzel Source <http://tonimenzel.com>
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
