Re: svn commit: r1071005 - /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/util/concurrent/SynapseThreadPool.java

2011-02-16 Thread Hiranya Jayathilaka
This has caused a build failure. Please take a look. Thanks, Hiranya On Wed, Feb 16, 2011 at 12:03 AM, wrote: > Author: supun > Date: Tue Feb 15 18:33:50 2011 > New Revision: 1071005 > > URL: http://svn.apache.org/viewvc?rev=1071005&view=rev > Log: > changing the thread pool to have the default

Re: svn commit: r1071005 - /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/util/concurrent/SynapseThreadPool.java

2011-02-16 Thread Supun Kamburugamuva
Fixed it. Sorry for the trouble. Thanks, Supun.. On Wed, Feb 16, 2011 at 10:49 PM, Hiranya Jayathilaka wrote: > This has caused a build failure. Please take a look. > > Thanks, > Hiranya > > > On Wed, Feb 16, 2011 at 12:03 AM, wrote: > >> Author: supun >> Date: Tue Feb 15 18:33:50 2011 >> New R

Re: svn commit: r1071005 - /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/util/concurrent/SynapseThreadPool.java

2011-02-16 Thread Supun Kamburugamuva
This lead me to thinking, isn't it better to move to the JDK 1.6? Thanks, Supun.. On Thu, Feb 17, 2011 at 10:55 AM, Supun Kamburugamuva wrote: > Fixed it. Sorry for the trouble. > > Thanks, > Supun.. > > > On Wed, Feb 16, 2011 at 10:49 PM, Hiranya Jayathilaka < > hiranya...@gmail.com> wrote: > >

Re: svn commit: r1071005 - /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/util/concurrent/SynapseThreadPool.java

2011-02-17 Thread indika kumara
Should it not had been done for 2.0? We can say 1.x and 2.x not compatible but 2 and 2.x ? ~ Indika On Thu, Feb 17, 2011 at 12:48 PM, Supun Kamburugamuva wrote: > This lead me to thinking, isn't it better to move to the JDK 1.6? > > Thanks, > Supun.. > > > On Thu, Feb 17, 2011 at 10:55 AM, Supu

Re: svn commit: r1071005 - /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/util/concurrent/SynapseThreadPool.java

2011-02-17 Thread indika kumara
I meant we should have done it for 2.0 as there were already API changes that made 1.x and 2.x incompatible. ~ Indika On Thu, Feb 17, 2011 at 2:46 PM, indika kumara wrote: > Should it not had been done for 2.0? We can say 1.x and 2.x not compatible > but 2 and 2.x ? > > ~ Indika > > > On Thu, F