Re: [dbutils] Consider moving Mock classes from src/test to src/java

2009-09-01 Thread Julien Aymé
2009/9/2 Jochen Wiedmann : > On Tue, Sep 1, 2009 at 10:29 PM, Dan Fabulich wrote: > >> Filing a JIRA issue wouldn't hurt, but I'm not sure we'd want to ship our >> mocks as part of the product.  I think there are better implementations of >> MockResultSet out there (SQLUnit, Mockrunner, etc.) > > W

Re: [dbutils] Consider moving Mock classes from src/test to src/java

2009-09-01 Thread Jochen Wiedmann
On Tue, Sep 1, 2009 at 10:29 PM, Dan Fabulich wrote: > Filing a JIRA issue wouldn't hurt, but I'm not sure we'd want to ship our > mocks as part of the product.  I think there are better implementations of > MockResultSet out there (SQLUnit, Mockrunner, etc.) Why not simply publish the test jar?

[g...@vmgump]: Project commons-jelly-tags-jaxme (in module commons-jelly) failed

2009-09-01 Thread commons-jelly-tags-jaxme development
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-jelly-tags-jaxme has an issue affecting its community integration

[g...@vmgump]: Project commons-jelly-tags-fmt-test (in module commons-jelly) failed

2009-09-01 Thread commons-jelly-tags-fmt development
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-jelly-tags-fmt-test has an issue affecting its community integrat

Re: [dbutils] Consider moving Mock classes from src/test to src/java

2009-09-01 Thread Dan Fabulich
Julien Aymé wrote: What do you think? Should I create a JIRA issue for this? Filing a JIRA issue wouldn't hurt, but I'm not sure we'd want to ship our mocks as part of the product. I think there are better implementations of MockResultSet out there (SQLUnit, Mockrunner, etc.) -Dan --

[g...@vmgump]: Project commons-configuration-test (in module apache-commons) failed

2009-09-01 Thread Gump
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-configuration-test has an issue affecting its community integrati

Re: a question regarding maxactive

2009-09-01 Thread sebb
On 01/09/2009, Chen Bangzhong wrote: > Hi, experts > > I have one java web application. In the application, several datasource was > configured for dbcp. For each datasource, maxActive was set to 100 and max > Idle set to 30. This is a question for the Commons User list. See: http://commons.a

a question regarding maxactive

2009-09-01 Thread Chen Bangzhong
Hi, experts I have one java web application. In the application, several datasource was configured for dbcp. For each datasource, maxActive was set to 100 and max Idle set to 30. Then I used several crawlers to make the web application very busy, until the application reported that it can't ge

Re: [JEXL] 2.0 change of behaviour for expressions - RFC

2009-09-01 Thread sebb
On 01/09/2009, Henrib wrote: > > Correction, the behavior has *not* changed in the current trunk. > An expression with multiple statements still logs a warning upon creation > and only executes its first child. > Checked with: > > public void testSebb() throws Exception { > JexlContex

Re: [JEXL] 2.0 change of behaviour for expressions - RFC

2009-09-01 Thread Henrib
Correction, the behavior has *not* changed in the current trunk. An expression with multiple statements still logs a warning upon creation and only executes its first child. Checked with: public void testSebb() throws Exception { JexlContext ctxt = JexlHelper.createContext(); Jexl

[JEXL] 2.0 change of behaviour for expressions - RFC

2009-09-01 Thread sebb
The latest set of SVN updates have changed the behaviour of JEXL 2.0 expressions containing multiple statements, e.g. "1;2;3;" Previously, the whole script was parsed, but only the first statement in the expression was evaluated, and a warning message was logged: WARNING: The JEXL Expression crea