date:20070718

Author: psteitz
Date: Tue Jul 17 23:06:59 2007
New Revision: 557160

URL: http://svn.apache.org/viewvc?view=revrev=557160
Log:
Fixed directory structure.

Added:
jakarta/commons/sandbox/performance/branches/
jakarta/commons/sandbox/performance/tags/
jakarta/commons/sandbox/performance/trunk/
jakarta/commons/sandbox/performance/trunk/build.properties
  - copied unchanged from r556823, 
jakarta/commons/sandbox/performance/build.properties
jakarta/commons/sandbox/performance/trunk/build.xml
  - copied unchanged from r556823, 
jakarta/commons/sandbox/performance/build.xml
jakarta/commons/sandbox/performance/trunk/config.xml
  - copied unchanged from r556823, 
jakarta/commons/sandbox/performance/config.xml
jakarta/commons/sandbox/performance/trunk/logging.properties
  - copied unchanged from r556823, 
jakarta/commons/sandbox/performance/logging.properties
jakarta/commons/sandbox/performance/trunk/src/
  - copied from r556823, jakarta/commons/sandbox/performance/src/
Removed:
jakarta/commons/sandbox/performance/build.properties
jakarta/commons/sandbox/performance/build.xml
jakarta/commons/sandbox/performance/config.xml
jakarta/commons/sandbox/performance/logging.properties
jakarta/commons/sandbox/performance/src/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r557162 - /jakarta/commons/trunks-sandbox/

Author: psteitz
Date: Tue Jul 17 23:12:17 2007
New Revision: 557162

URL: http://svn.apache.org/viewvc?view=revrev=557162
Log:
Adding performance to sandbox

Modified:
jakarta/commons/trunks-sandbox/   (props changed)

Propchange: jakarta/commons/trunks-sandbox/
--
--- svn:externals (original)
+++ svn:externals Tue Jul 17 23:12:17 2007
@@ -9,5 +9,6 @@
 javaflow 
https://svn.apache.org/repos/asf/jakarta/commons/sandbox/javaflow/trunk
 js2j https://svn.apache.org/repos/asf/jakarta/commons/sandbox/js2j/trunk
 openpgp https://svn.apache.org/repos/asf/jakarta/commons/sandbox/openpgp/trunk
+performance 
https://svn.apache.org/repos/asf/jakarta/commons/sandbox/performance/trunk
 pipeline 
https://svn.apache.org/repos/asf/jakarta/commons/sandbox/pipeline/trunk
 proxy https://svn.apache.org/repos/asf/jakarta/commons/sandbox/proxy/trunk



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r557176 - in /jakarta/commons/proper/dbcp/trunk: src/java/org/apache/commons/dbcp/ src/java/org/apache/commons/dbcp/cpdsadapter/ src/test/org/apache/commons/dbcp/ src/test/org/apache/commo

Author: psteitz
Date: Tue Jul 17 23:46:16 2007
New Revision: 557176

URL: http://svn.apache.org/viewvc?view=revrev=557176
Log:
Changed behavior to allow Connection, Statement, PreparedStatement,
CallableStatement and ResultSet to be closed multiple times. The first time
close is called the resource is closed and any subsequent calls have no effect.
This behavior is required as per the JavaDocs for these classes. Also added
tests for closing all types multiple times and updated any tests that
incorrectly assert that a resource can not be closed more then once.

JIRA: DBCP-233
Patch provided by Dain Sundstrom
Fixes DBCP-134, DBCP-3

Modified:

jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingConnection.java

jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolablePreparedStatement.java

jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolingDataSource.java

jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolingDriver.java

jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/cpdsadapter/ConnectionImpl.java

jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/TestConnectionPool.java

jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/TestManual.java

jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/TesterResultSet.java

jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/TesterStatement.java

jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/managed/TestManagedDataSource.java
jakarta/commons/proper/dbcp/trunk/xdocs/changes.xml

Modified: 
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingConnection.java
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingConnection.java?view=diffrev=557176r1=557175r2=557176
==
--- 
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingConnection.java
 (original)
+++ 
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingConnection.java
 Tue Jul 17 23:46:16 2007
@@ -208,10 +208,17 @@
  * Closes the underlying connection, and close
  * any Statements that were not explicitly closed.
  */
-public void close() throws SQLException
-{
-passivate();
-_conn.close();
+public void close() throws SQLException {
+// close can be called multiple times, but PoolableConnection 
improperly
+// throws an exception when a connection is closed twice, so before 
calling
+// close we aren't alreayd closed
+if (!isClosed()) {
+try {
+_conn.close();
+} finally {
+_closed = true;
+}
+}
 }
 
 protected void handleException(SQLException e) throws SQLException {

Modified: 
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolablePreparedStatement.java
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolablePreparedStatement.java?view=diffrev=557176r1=557175r2=557176
==
--- 
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolablePreparedStatement.java
 (original)
+++ 
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolablePreparedStatement.java
 Tue Jul 17 23:46:16 2007
@@ -72,9 +72,8 @@
  * Return me to my pool.
  */
 public void close() throws SQLException {
-if(isClosed()) {
-throw new SQLException(Already closed);
-} else {
+// calling close twice should have no effect
+if (!isClosed()) {
 try {
 _pool.returnObject(_key,this);
 } catch(SQLException e) {

Modified: 
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolingDataSource.java
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolingDataSource.java?view=diffrev=557176r1=557175r2=557176
==
--- 
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolingDataSource.java
 (original)
+++ 
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolingDataSource.java
 Tue Jul 17 23:46:16 2007
@@ -177,10 +177,11 @@
 }
 
 public void close() throws SQLException {
-checkOpen();
-this.delegate.close();
-this.delegate = null;
-super.setDelegate(null);
+if (delegate != null) {
+this.delegate.close();
+this.delegate = null;
+super.setDelegate(null);
+}
 }
 
 public boolean

[jira] Resolved: (DBCP-233) Allow connection, statement, and result set to be closed multiple times


 [ 
https://issues.apache.org/jira/browse/DBCP-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Phil Steitz resolved DBCP-233.
--

Resolution: Fixed

Patch applied.  Many thanks.

 Allow connection, statement, and result set to be closed multiple times
 ---

 Key: DBCP-233
 URL: https://issues.apache.org/jira/browse/DBCP-233
 Project: Commons Dbcp
  Issue Type: Improvement
Reporter: Dain Sundstrom
 Fix For: 1.3

 Attachments: CloseTwice.patch


 This patch allows Connection, Statement, PreparedStatement, CallableStatement 
 and ResultSet to be closed multiple times.  The first time close is called 
 the resource is closed and any subsequent calls have no effect.  This 
 behavior is required as per the JavaDocs for these classes.  The patch adds 
 tests for closing all types multiple times and updates any tests that 
 incorrectly assert that a resource can be closed more then once.
 This patch fixes DBCP-134 and DBCP-3

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (DBCP-134) [dbcp] DelegatingConnection.close() throws exception


 [ 
https://issues.apache.org/jira/browse/DBCP-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Phil Steitz resolved DBCP-134.
--

Resolution: Fixed

Fixed in r 557176.

 [dbcp] DelegatingConnection.close() throws exception
 

 Key: DBCP-134
 URL: https://issues.apache.org/jira/browse/DBCP-134
 Project: Commons Dbcp
  Issue Type: Bug
Affects Versions: Nightly Builds
 Environment: Operating System: Mac OS X 10.3
 Platform: Macintosh
Reporter: Hilmar Lapp
Priority: Critical
 Fix For: 1.3


 Closing connections that were obtained from PoolingDataSource und wrapped 
 with a 
 DelegatingConnection throws a 'java.sql.SQLException: Already closed' when 
 calling close() on them in 
 order to return the connection to the underlying pool.
 The reason is code in DelegatingConnection.passivate() the motivation for 
 which I don't completely 
 understand.
 At any rate, here is what happens. DelegatingConnection.close() calls 
 passivate() before actually closing 
 the delegate: 
 /**
  * Closes the underlying connection, and close
  * any Statements that were not explicitly closed.
  */
 public void close() throws SQLException
 {
 passivate();
 _conn.close();
 }
 DelegatingConnection.passivate() in turn cleans up statements and, if the 
 delegate is a 
 DelegatingConnection too, calls passivate() on the delegate. Finally, the 
 instance variable _closed is set 
 to true:
 protected void passivate() throws SQLException {
 try {
 // ... some statement clean up work, then: 
 if(_conn instanceof DelegatingConnection) {
 ((DelegatingConnection)_conn).passivate();
 }
 }
 finally {
 _closed = true;
 }
 }
 When this finishes and the delegate is indeed itself a delegating connection, 
 close() will call 
 _conn.close(). If DelegatingConnection were final this would even work, but 
 it is not (on purpose). A 
 notable derived class is PoolableConnection, which overrides close() and 
 throws an exception if it is 
 called when isClosed() returns true. isClosed() returns true if the _closed 
 instance variable is true. 
 BUMMER.
 The problem surfaces as soon as one tries to wrap the connection returned by 
 PoolingDataSource with 
 another DelegatingConnections, which happens to be what I do.
 I noticed this when I upgraded from 1.1 to 1.2.1, and it's still there in the 
 nightly snapshot.
 There are several design decisions that I think deserve a critical look:
 - why does passivate() set a variable that effectively decides whether a 
 connection is considered 
 closed or not? shouldn't only close() be doing that?
  
 - why does DelegatingConnection even bother to clean up statements when 
 those statements by 
 definition must have come from the delegate (or its delegate and so forth) 
 and so are the responsibility 
 of the delegate (creator) to clean up
 - by propagating passivate() in the same method to the delegate if the 
 delegate delegates itself 
 DelegatingConnection is making assumptions that may be (and in fact are) 
 easily violated if someone 
 sub-classes DelegatingConnection and the delegate is now a subclass with 
 possibly altered behavior. 
 Why does it not suffice to expect that calling close() on the delegate will 
 give the delegate enough 
 chance to clean up itself, regardless of the implementing class of the 
 delegate.
 I'd be thrilled if this can be fixed quickly, and fixing any of the problems 
 pinpointed above will fix the 
 issue. Or so I think.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (DBCP-3) [dbcp] PoolableConnection.close() won't allow multiple close


 [ 
https://issues.apache.org/jira/browse/DBCP-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Phil Steitz resolved DBCP-3.


Resolution: Fixed

Fixed in r 557176.

 [dbcp] PoolableConnection.close() won't allow multiple close
 

 Key: DBCP-3
 URL: https://issues.apache.org/jira/browse/DBCP-3
 Project: Commons Dbcp
  Issue Type: Bug
Affects Versions: Nightly Builds
 Environment: Operating System: All
 Platform: All
Reporter: Adam Jenkins
 Fix For: 1.3


 Sun's javadoc for java.sql.Connection.close() specifies that calling close on 
 an
 already closed Connection is a no-op.  However, PoolableConnection.close() (v
 1.10) throws a SQLException if close() is called on a closed Connection. 
 PoolableConnection.close() should just return if the Connection is already
 closed.  Here is a patch:
 To demonstrate the bug, just obtain an open PoolableConnection and call 
 close()
 on it twice; the second call will produce a SQLException.  According to Sun's
 spec, the second close() should just be a no-op.  The current behaviour is
 preferable to the old behaviour where it returned the Connection to the pool
 twice, but it's still not according to the spec.
 Here's a patch:
 *** PoolableConnection.java.orig2003-09-15 16:07:53.0 -0400
 --- PoolableConnection.java 2003-09-15 16:08:11.0 -0400
 ***
 *** 108,114 
*/
public synchronized void close() throws SQLException {
   if(isClosed()) {
 ! throw new SQLException(Already closed.);
   } else {
   try {
   _pool.returnObject(this);
 --- 108,114 
*/
public synchronized void close() throws SQLException {
   if(isClosed()) {
 ! return;
   } else {
   try {
   _pool.returnObject(this);

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (NET-163) [contribution] DNS utils

2007-07-18 Thread Nikolay Chugunov (JIRA)

[
https://issues.apache.org/jira/browse/NET-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513486
]

Nikolay Chugunov commented on NET-163:
--

Rory

The code is tested on JDK 1.4, 1.5 and 6. The code isn't tested on JDK 1.3
because Sun says that this JDK is not supported further:
http://java.sun.com/j2se/1.3/download.html

[contribution] DNS utils

Key: NET-163
URL: https://issues.apache.org/jira/browse/NET-163
Project: Commons Net
Issue Type: New Feature
Reporter: Nikolay Chugunov
Attachments: dnsutils.zip

Hi all,
I developed DNS methods for resolving IP address by host name and vice verse;
receiving mail exchange and authoritative name servers for domain; and
receiving other information about domain from DNS server.
JDK provides above functionality in JNDI DNS service provider [1]. But JNDI
technology is too abstract and obfuscates communication with DNS servers,
which leads to users don't use JNDI DNS SP.
Attached classes provide evident API for receiving information from DNS
server as wrapper for JNDI DNS SP. Also these classes provide necessary
additional parsing of answers.
Examples how to use created API can be found in DNSClientTest unit test. This
library requires only JDK and JUnit to run the test.
[1] http://java.sun.com/javase/6/docs/technotes/guides/jndi/jndi-dns.html

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[EMAIL PROTECTED]: Project commons-id (in module jakarta-commons-sandbox) failed

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 [EMAIL PROTECTED]

Project commons-id has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 3 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-id :  Commons Identifier Package


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-id-18072007.jar] identifier set to project name
 -DEBUG- (Gump generated) Maven Properties in: 
/srv/gump/public/workspace/jakarta-commons-sandbox/id/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/jakarta-commons-sandbox/id/project.xml
 -DEBUG- Maven project properties in: 
/srv/gump/public/workspace/jakarta-commons-sandbox/id/project.properties
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/gump_work/build_jakarta-commons-sandbox_commons-id.html
Work Name: build_jakarta-commons-sandbox_commons-id (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: maven --offline jar 
[Working Directory: /srv/gump/public/workspace/jakarta-commons-sandbox/id]
CLASSPATH: 
/usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/jakarta-commons/discovery/dist/commons-discovery.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-18072007.jar:/srv/gump/public/workspace/junit/dist/junit-18072007.jar:/srv/gump/packages/maven-cobertura-plugin/maven-cobertura-plugin-1.1.jar:/srv/gump/packages/maven-xdoc-plugin/maven-xdoc-plugin-1.9.2.jar
-
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

The build cannot continue because of the following unsatisfied dependencies:

dom4j-1.4.jar
commons-jelly-1.0-RC1.jar
commons-jelly-tags-jsl-1.0.jar
commons-jelly-tags-log-1.0.jar
commons-jelly-tags-velocity-1.0.jar
commons-jelly-tags-xml-1.1.jar (try downloading from 
http://jakarta.apache.org/commons/jelly/libs/xml/)
maven-1.0.2.jar
maven-model-3.0.0.jar
velocity-1.4.jar
commons-jelly-tags-fmt-1.0.jar

Total time: 2 seconds
Finished at: Wed Jul 18 01:22:13 GMT-08:00 2007

-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 0418072007, vmgump:vmgump-public:0418072007
Gump E-mail Identifier (unique within run) #32.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[EMAIL PROTECTED]: Project commons-id (in module jakarta-commons-sandbox) failed

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 [EMAIL PROTECTED]

Project commons-id has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 3 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-id :  Commons Identifier Package


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-id-18072007.jar] identifier set to project name
 -DEBUG- (Gump generated) Maven Properties in: 
/srv/gump/public/workspace/jakarta-commons-sandbox/id/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/jakarta-commons-sandbox/id/project.xml
 -DEBUG- Maven project properties in: 
/srv/gump/public/workspace/jakarta-commons-sandbox/id/project.properties
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/gump_work/build_jakarta-commons-sandbox_commons-id.html
Work Name: build_jakarta-commons-sandbox_commons-id (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: maven --offline jar 
[Working Directory: /srv/gump/public/workspace/jakarta-commons-sandbox/id]
CLASSPATH: 
/usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/jakarta-commons/discovery/dist/commons-discovery.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-18072007.jar:/srv/gump/public/workspace/junit/dist/junit-18072007.jar:/srv/gump/packages/maven-cobertura-plugin/maven-cobertura-plugin-1.1.jar:/srv/gump/packages/maven-xdoc-plugin/maven-xdoc-plugin-1.9.2.jar
-
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

The build cannot continue because of the following unsatisfied dependencies:

dom4j-1.4.jar
commons-jelly-1.0-RC1.jar
commons-jelly-tags-jsl-1.0.jar
commons-jelly-tags-log-1.0.jar
commons-jelly-tags-velocity-1.0.jar
commons-jelly-tags-xml-1.1.jar (try downloading from 
http://jakarta.apache.org/commons/jelly/libs/xml/)
maven-1.0.2.jar
maven-model-3.0.0.jar
velocity-1.4.jar
commons-jelly-tags-fmt-1.0.jar

Total time: 2 seconds
Finished at: Wed Jul 18 01:22:13 GMT-08:00 2007

-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 0418072007, vmgump:vmgump-public:0418072007
Gump E-mail Identifier (unique within run) #32.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed

2007-07-18 Thread commons-jelly-tags-jsl 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 [EMAIL PROTECTED]

Project commons-jelly-tags-jsl-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 3 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-jsl-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on ant exists, no need to add for property 
maven.jar.ant-optional.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- (Gump generated) Maven Properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml
 -DEBUG- Maven project properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties
 -INFO- Project Reports in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/gump_work/build_commons-jelly_commons-jelly-tags-jsl-test.html
Work Name: build_commons-jelly_commons-jelly-tags-jsl-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 12 secs
Command Line: maven --offline jar 
[Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/jsl]
CLASSPATH: 
/usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/srv/gump/public/workspace/commons-cli-1.0.x/target/commons-cli-18072007.jar:/srv/gump/public/workspace/jakarta-commons/collections/build/commons-collections-18072007.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-18072007.jar:/srv/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-18072007.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-18072007.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar
-
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:64)
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:59)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:263)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187)
[junit] at 
org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:66)
[junit] at 
org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:113)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187)
[junit] at 
org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:161)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:80)
[junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:102)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:91)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:78)
[junit]

[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed

2007-07-18 Thread commons-jelly-tags-jsl 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 [EMAIL PROTECTED]

Project commons-jelly-tags-jsl-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 3 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-jsl-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on ant exists, no need to add for property 
maven.jar.ant-optional.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- (Gump generated) Maven Properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml
 -DEBUG- Maven project properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties
 -INFO- Project Reports in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/gump_work/build_commons-jelly_commons-jelly-tags-jsl-test.html
Work Name: build_commons-jelly_commons-jelly-tags-jsl-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 12 secs
Command Line: maven --offline jar 
[Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/jsl]
CLASSPATH: 
/usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/srv/gump/public/workspace/commons-cli-1.0.x/target/commons-cli-18072007.jar:/srv/gump/public/workspace/jakarta-commons/collections/build/commons-collections-18072007.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-18072007.jar:/srv/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-18072007.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-18072007.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar
-
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:64)
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:59)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:263)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187)
[junit] at 
org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:66)
[junit] at 
org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:113)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187)
[junit] at 
org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:161)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:80)
[junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:102)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:91)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:78)
[junit]

[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) failed

2007-07-18 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 [EMAIL PROTECTED]

Project commons-jelly-tags-jaxme has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 3 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-jaxme :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-jelly-tags-jaxme-18072007.jar] identifier set to 
project name
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme.
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme-js.
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme-xs.
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme-api.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- (Gump generated) Maven Properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/project.xml
 -DEBUG- Maven project properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/project.properties
 -INFO- Project Reports in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/target/test-reports
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/gump_work/build_commons-jelly_commons-jelly-tags-jaxme.html
Work Name: build_commons-jelly_commons-jelly-tags-jaxme (Type: Build)
Work ended in a state of : Failed
Elapsed: 9 secs
Command Line: maven --offline jar 
[Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme]
CLASSPATH: 
/usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/srv/gump/public/workspace/jakarta-commons/collections/build/commons-collections-18072007.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xmlunit/target/commons-jelly-tags-xmlunit-18072007.jar:/srv/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-18072007.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-18072007.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxme2-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmeapi-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmejs-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmexs-0.5.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/xmlunit/build/lib/xmlunit-18072007.jar
-
[javac] symbol  : variable super
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler
[javac]   super.characters(pChars, pOffset, pLen);
[javac]   ^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:305:
 cannot find symbol
[javac] symbol  : variable super
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler
[javac] super.init(pData);
[javac] ^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:315:
 cannot find symbol
[javac] symbol  : method getData()
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler
[javac] __handler_Name.init(getData());
[javac] ^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressHandler.java:22:
 cannot find symbol
[javac] symbol  : method getData()
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressHandler

[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) failed

2007-07-18 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 [EMAIL PROTECTED]

Project commons-jelly-tags-jaxme has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 3 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-jaxme :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-jelly-tags-jaxme-18072007.jar] identifier set to 
project name
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme.
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme-js.
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme-xs.
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme-api.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- (Gump generated) Maven Properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/project.xml
 -DEBUG- Maven project properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/project.properties
 -INFO- Project Reports in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/target/test-reports
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/gump_work/build_commons-jelly_commons-jelly-tags-jaxme.html
Work Name: build_commons-jelly_commons-jelly-tags-jaxme (Type: Build)
Work ended in a state of : Failed
Elapsed: 9 secs
Command Line: maven --offline jar 
[Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme]
CLASSPATH: 
/usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/srv/gump/public/workspace/jakarta-commons/collections/build/commons-collections-18072007.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xmlunit/target/commons-jelly-tags-xmlunit-18072007.jar:/srv/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-18072007.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-18072007.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxme2-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmeapi-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmejs-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmexs-0.5.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/xmlunit/build/lib/xmlunit-18072007.jar
-
[javac] symbol  : variable super
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler
[javac]   super.characters(pChars, pOffset, pLen);
[javac]   ^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:305:
 cannot find symbol
[javac] symbol  : variable super
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler
[javac] super.init(pData);
[javac] ^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:315:
 cannot find symbol
[javac] symbol  : method getData()
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler
[javac] __handler_Name.init(getData());
[javac] ^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressHandler.java:22:
 cannot find symbol
[javac] symbol  : method getData()
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressHandler

[jira] Created: (DAEMON-101) Javadoc typo, says avfter should probably be after

2007-07-18 Thread Tim Mooney (JIRA)

Javadoc typo, says avfter should probably be after
--

 Key: DAEMON-101
 URL: https://issues.apache.org/jira/browse/DAEMON-101
 Project: Commons Daemon
  Issue Type: Improvement
 Environment: N/A, javadoc
Reporter: Tim Mooney
Priority: Trivial


Javadoc for the Daemon interface method start uses the word avfter, should 
probably be after.

Full comment:
Start the operation of this Daemon instance. This method is to be invoked by 
the environment after the init() method has been successfully invoked and 
possibly the security level of the JVM has been dropped. Implementors of this 
method are free to start any number of threads, but need to return control 
avfter having done that to enable invocation of the stop()-method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (DAEMON-101) Javadoc typo, says avfter should probably be after

2007-07-18 Thread Tim Mooney (JIRA)


 [ 
https://issues.apache.org/jira/browse/DAEMON-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Mooney updated DAEMON-101:
--

Description: 
Javadoc for the Daemon interface method start uses the word avfter, should 
probably be after.  The comment may also fail to close a code tag (which 
doesn't seem to be valid, anyway).

Full comment:
Start the operation of this Daemon instance. This method is to be invoked by 
the environment after the init() method has been successfully invoked and 
possibly the security level of the JVM has been dropped. Implementors of this 
method are free to start any number of threads, but need to return control 
avfter having done that to enable invocation of the stop()-method.

  was:
Javadoc for the Daemon interface method start uses the word avfter, should 
probably be after.

Full comment:
Start the operation of this Daemon instance. This method is to be invoked by 
the environment after the init() method has been successfully invoked and 
possibly the security level of the JVM has been dropped. Implementors of this 
method are free to start any number of threads, but need to return control 
avfter having done that to enable invocation of the stop()-method.


 Javadoc typo, says avfter should probably be after
 --

 Key: DAEMON-101
 URL: https://issues.apache.org/jira/browse/DAEMON-101
 Project: Commons Daemon
  Issue Type: Improvement
 Environment: N/A, javadoc
Reporter: Tim Mooney
Priority: Trivial

 Javadoc for the Daemon interface method start uses the word avfter, should 
 probably be after.  The comment may also fail to close a code tag (which 
 doesn't seem to be valid, anyway).
 Full comment:
 Start the operation of this Daemon instance. This method is to be invoked by 
 the environment after the init() method has been successfully invoked and 
 possibly the security level of the JVM has been dropped. Implementors of this 
 method are free to start any number of threads, but need to return control 
 avfter having done that to enable invocation of the stop()-method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (JELLY-278) Missing link to SVN repository (not WebSVN)

2007-07-18 Thread Stepan Koltsov (JIRA)

Missing link to SVN repository (not WebSVN)
---

 Key: JELLY-278
 URL: https://issues.apache.org/jira/browse/JELLY-278
 Project: Commons Jelly
  Issue Type: Wish
Reporter: Stepan Koltsov


On the page

http://jakarta.apache.org/commons/jelly/cvs-usage.html

there iis only link to websvn, and I don't know where can I download sources 
from.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (JELLY-278) Missing link to SVN repository (not WebSVN)

2007-07-18 Thread Lukas Theussl (JIRA)


[ 
https://issues.apache.org/jira/browse/JELLY-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513609
 ] 

Lukas Theussl commented on JELLY-278:
-

Somebody has to re-publish the site, see JELLY-272. The link to my own jelly 
site that I gave there is still valid, you can get the information you need 
from there.

 Missing link to SVN repository (not WebSVN)
 ---

 Key: JELLY-278
 URL: https://issues.apache.org/jira/browse/JELLY-278
 Project: Commons Jelly
  Issue Type: Wish
Reporter: Stepan Koltsov

 On the page
 http://jakarta.apache.org/commons/jelly/cvs-usage.html
 there iis only link to websvn, and I don't know where can I download sources 
 from.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[EMAIL PROTECTED]: Project commons-id (in module jakarta-commons-sandbox) failed

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 [EMAIL PROTECTED]

Project commons-id has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-id :  Commons Identifier Package


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-id-18072007.jar] identifier set to project name
 -DEBUG- (Gump generated) Maven Properties in: 
/srv/gump/public/workspace/jakarta-commons-sandbox/id/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/jakarta-commons-sandbox/id/project.xml
 -DEBUG- Maven project properties in: 
/srv/gump/public/workspace/jakarta-commons-sandbox/id/project.properties
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/gump_work/build_jakarta-commons-sandbox_commons-id.html
Work Name: build_jakarta-commons-sandbox_commons-id (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: maven --offline jar 
[Working Directory: /srv/gump/public/workspace/jakarta-commons-sandbox/id]
CLASSPATH: 
/usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/jakarta-commons/discovery/dist/commons-discovery.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-18072007.jar:/srv/gump/public/workspace/junit/dist/junit-18072007.jar:/srv/gump/packages/maven-cobertura-plugin/maven-cobertura-plugin-1.1.jar:/srv/gump/packages/maven-xdoc-plugin/maven-xdoc-plugin-1.9.2.jar
-
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

The build cannot continue because of the following unsatisfied dependencies:

dom4j-1.4.jar
commons-jelly-1.0-RC1.jar
commons-jelly-tags-jsl-1.0.jar
commons-jelly-tags-log-1.0.jar
commons-jelly-tags-velocity-1.0.jar
commons-jelly-tags-xml-1.1.jar (try downloading from 
http://jakarta.apache.org/commons/jelly/libs/xml/)
maven-1.0.2.jar
maven-model-3.0.0.jar
velocity-1.4.jar
commons-jelly-tags-fmt-1.0.jar

Total time: 2 seconds
Finished at: Wed Jul 18 09:40:43 GMT-08:00 2007

-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 06000818072007, vmgump:vmgump-public:06000818072007
Gump E-mail Identifier (unique within run) #8.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[EMAIL PROTECTED]: Project commons-id (in module jakarta-commons-sandbox) failed

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 [EMAIL PROTECTED]

Project commons-id has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-id :  Commons Identifier Package


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-id-18072007.jar] identifier set to project name
 -DEBUG- (Gump generated) Maven Properties in: 
/srv/gump/public/workspace/jakarta-commons-sandbox/id/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/jakarta-commons-sandbox/id/project.xml
 -DEBUG- Maven project properties in: 
/srv/gump/public/workspace/jakarta-commons-sandbox/id/project.properties
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/gump_work/build_jakarta-commons-sandbox_commons-id.html
Work Name: build_jakarta-commons-sandbox_commons-id (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: maven --offline jar 
[Working Directory: /srv/gump/public/workspace/jakarta-commons-sandbox/id]
CLASSPATH: 
/usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/jakarta-commons/discovery/dist/commons-discovery.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-18072007.jar:/srv/gump/public/workspace/junit/dist/junit-18072007.jar:/srv/gump/packages/maven-cobertura-plugin/maven-cobertura-plugin-1.1.jar:/srv/gump/packages/maven-xdoc-plugin/maven-xdoc-plugin-1.9.2.jar
-
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

The build cannot continue because of the following unsatisfied dependencies:

dom4j-1.4.jar
commons-jelly-1.0-RC1.jar
commons-jelly-tags-jsl-1.0.jar
commons-jelly-tags-log-1.0.jar
commons-jelly-tags-velocity-1.0.jar
commons-jelly-tags-xml-1.1.jar (try downloading from 
http://jakarta.apache.org/commons/jelly/libs/xml/)
maven-1.0.2.jar
maven-model-3.0.0.jar
velocity-1.4.jar
commons-jelly-tags-fmt-1.0.jar

Total time: 2 seconds
Finished at: Wed Jul 18 09:40:43 GMT-08:00 2007

-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 06000818072007, vmgump:vmgump-public:06000818072007
Gump E-mail Identifier (unique within run) #8.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (NET-163) [contribution] DNS utils

2007-07-18 Thread Daniel Savarese (JIRA)

[
https://issues.apache.org/jira/browse/NET-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513653
]

Daniel Savarese commented on NET-163:
-

Attached classes provide evident API for receiving information from DNS serv
er as wrapper for JNDI DNS SP. Also these classes provide necessary additional

I have yet to look at the code, but I think it's important to remember that
Commons Net has all along been an implementation of protocols at the lowest
level and not a wrapper library. Wrapping JNDI seems out of scope to me
because Commons Net is supposed to be the sort of thing that sits a layer
underneath JNDI (e.g., a JNDI implementation would use a Commons Net
DNS implementation; not the other way around). At any rate, that's my
initial reaction.

Also, any substantial code contributions have to go through the proper
paperwork. And we need to start pulling in people who contribute code
as committers instead of letting them dump off a hefty chunk of code
and disappearing as has happened a couple of times (although in at
least one case, I think the contributor became a committer). Not that
I've been a particularly active contributor of late ...

At any rate, just a couple of thoughts to consider before accepting
more Commons Net contributions.

[contribution] DNS utils

Key: NET-163
URL: https://issues.apache.org/jira/browse/NET-163
Project: Commons Net
Issue Type: New Feature
Reporter: Nikolay Chugunov
Attachments: dnsutils.zip

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (LANG-349) Deadlock using ReflectionToStringBuilder

2007-07-18 Thread David Ishee (JIRA)

Deadlock using ReflectionToStringBuilder


 Key: LANG-349
 URL: https://issues.apache.org/jira/browse/LANG-349
 Project: Commons Lang
  Issue Type: Bug
Affects Versions: 2.0
 Environment: java version 1.5.0_10
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)

uname -a
Linux fwjsfimat04 2.4.21-32.EL #1 SMP Fri Apr 15 21:02:58 EDT 2005 x86_64 
x86_64 x86_64 GNU/Linux

Reporter: David Ishee
Priority: Critical


I used the ReflectionToStringBuilder on an object to output debugging messages 
to Log4j. If this object was picked up by two different threads and the 
toString() method was called at the same time in two different threads, a 
deadlock occurrs.

Here is a stack trace from using jstack:

{noformat}
Thread 1172: (state = BLOCKED)
 - java.util.Vector.hashCode() @bci=0, line=938 (Interpreted frame)
 - java.util.HashMap.containsKey(java.lang.Object) @bci=6, line=377 (Compiled 
frame)
 - org.apache.commons.lang.builder.ReflectionToStringBuilder.toString() 
@bci=50, line=522 (Compiled frame)
 - 
org.apache.commons.lang.builder.ReflectionToStringBuilder.toString(java.lang.Object,
 org.apache.commons.lang.builder.ToStringStyle, boolean, java.lang.Class) 
@bci=12, line=265 (Interpreted frame)
 - 
org.apache.commons.lang.builder.ReflectionToStringBuilder.toString(java.lang.Object,
 org.apache.commons.lang.builder.ToStringStyle) @bci=4, line=197 (Interpreted 
frame)
 - 
org.apache.commons.lang.builder.ToStringBuilder.reflectionToString(java.lang.Object,
 org.apache.commons.lang.builder.ToStringStyle) @bci=2, line=170 (Interpreted 
frame)
[...]
{noformat}

{noformat}
Thread 1191: (state = BLOCKED)
 - java.util.Vector.hashCode() @bci=0, line=938 (Interpreted frame)
 - java.util.HashMap.containsKey(java.lang.Object) @bci=6, line=377 (Compiled 
frame)
 - org.apache.commons.lang.builder.ReflectionToStringBuilder.toString() 
@bci=50, line=522 (Compiled frame)
 [...]

{noformat}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (LANG-349) Deadlock using ReflectionToStringBuilder

2007-07-18 Thread David Ishee (JIRA)


 [ 
https://issues.apache.org/jira/browse/LANG-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Ishee updated LANG-349:
-

Description: 
I used the ReflectionToStringBuilder on an object to output debugging messages 
to Log4j. If this object was picked up by two different threads and the 
toString() method was called at the same time in two different threads, a 
deadlock occurrs.

Here is a stack trace from using jstack:

Thread 1172: (state = BLOCKED)
 - java.util.Vector.hashCode() @bci=0, line=938 (Interpreted frame)
 - java.util.HashMap.containsKey(java.lang.Object) @bci=6, line=377 (Compiled 
frame)
 - org.apache.commons.lang.builder.ReflectionToStringBuilder.toString() 
@bci=50, line=522 (Compiled frame)
 - 
org.apache.commons.lang.builder.ReflectionToStringBuilder.toString(java.lang.Object,
 org.apache.commons.lang.builder.ToStringStyle, boolean, java.lang.Class) 
@bci=12, line=265 (Interpreted frame)
 - 
org.apache.commons.lang.builder.ReflectionToStringBuilder.toString(java.lang.Object,
 org.apache.commons.lang.builder.ToStringStyle) @bci=4, line=197 (Interpreted 
frame)
 - 
org.apache.commons.lang.builder.ToStringBuilder.reflectionToString(java.lang.Object,
 org.apache.commons.lang.builder.ToStringStyle) @bci=2, line=170 (Interpreted 
frame)
[...]

Thread 1191: (state = BLOCKED)
 - java.util.Vector.hashCode() @bci=0, line=938 (Interpreted frame)
 - java.util.HashMap.containsKey(java.lang.Object) @bci=6, line=377 (Compiled 
frame)
 - org.apache.commons.lang.builder.ReflectionToStringBuilder.toString() 
@bci=50, line=522 (Compiled frame)
 [...]



  was:
I used the ReflectionToStringBuilder on an object to output debugging messages 
to Log4j. If this object was picked up by two different threads and the 
toString() method was called at the same time in two different threads, a 
deadlock occurrs.

Here is a stack trace from using jstack:

{noformat}
Thread 1172: (state = BLOCKED)
 - java.util.Vector.hashCode() @bci=0, line=938 (Interpreted frame)
 - java.util.HashMap.containsKey(java.lang.Object) @bci=6, line=377 (Compiled 
frame)
 - org.apache.commons.lang.builder.ReflectionToStringBuilder.toString() 
@bci=50, line=522 (Compiled frame)
 - 
org.apache.commons.lang.builder.ReflectionToStringBuilder.toString(java.lang.Object,
 org.apache.commons.lang.builder.ToStringStyle, boolean, java.lang.Class) 
@bci=12, line=265 (Interpreted frame)
 - 
org.apache.commons.lang.builder.ReflectionToStringBuilder.toString(java.lang.Object,
 org.apache.commons.lang.builder.ToStringStyle) @bci=4, line=197 (Interpreted 
frame)
 - 
org.apache.commons.lang.builder.ToStringBuilder.reflectionToString(java.lang.Object,
 org.apache.commons.lang.builder.ToStringStyle) @bci=2, line=170 (Interpreted 
frame)
[...]
{noformat}

{noformat}
Thread 1191: (state = BLOCKED)
 - java.util.Vector.hashCode() @bci=0, line=938 (Interpreted frame)
 - java.util.HashMap.containsKey(java.lang.Object) @bci=6, line=377 (Compiled 
frame)
 - org.apache.commons.lang.builder.ReflectionToStringBuilder.toString() 
@bci=50, line=522 (Compiled frame)
 [...]

{noformat}


 Deadlock using ReflectionToStringBuilder
 

 Key: LANG-349
 URL: https://issues.apache.org/jira/browse/LANG-349
 Project: Commons Lang
  Issue Type: Bug
Affects Versions: 2.0
 Environment: java version 1.5.0_10
 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
 Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
 uname -a
 Linux fwjsfimat04 2.4.21-32.EL #1 SMP Fri Apr 15 21:02:58 EDT 2005 x86_64 
 x86_64 x86_64 GNU/Linux
Reporter: David Ishee
Priority: Critical

 I used the ReflectionToStringBuilder on an object to output debugging 
 messages to Log4j. If this object was picked up by two different threads and 
 the toString() method was called at the same time in two different threads, a 
 deadlock occurrs.
 Here is a stack trace from using jstack:
 Thread 1172: (state = BLOCKED)
  - java.util.Vector.hashCode() @bci=0, line=938 (Interpreted frame)
  - java.util.HashMap.containsKey(java.lang.Object) @bci=6, line=377 (Compiled 
 frame)
  - org.apache.commons.lang.builder.ReflectionToStringBuilder.toString() 
 @bci=50, line=522 (Compiled frame)
  - 
 org.apache.commons.lang.builder.ReflectionToStringBuilder.toString(java.lang.Object,
  org.apache.commons.lang.builder.ToStringStyle, boolean, java.lang.Class) 
 @bci=12, line=265 (Interpreted frame)
  - 
 org.apache.commons.lang.builder.ReflectionToStringBuilder.toString(java.lang.Object,
  org.apache.commons.lang.builder.ToStringStyle) @bci=4, line=197 (Interpreted 
 frame)
  - 
 org.apache.commons.lang.builder.ToStringBuilder.reflectionToString(java.lang.Object,
  org.apache.commons.lang.builder.ToStringStyle) @bci=2, line=170 (Interpreted 
 frame)
 [...]
 Thread 1191: (state = BLOCKED)
  - java.util.Vector.hashCode()

[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed

2007-07-18 Thread commons-jelly-tags-jsl 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 [EMAIL PROTECTED]

Project commons-jelly-tags-jsl-test has an issue affecting its community 
integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-jsl-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on ant exists, no need to add for property 
maven.jar.ant-optional.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- (Gump generated) Maven Properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml
 -DEBUG- Maven project properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties
 -INFO- Project Reports in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/gump_work/build_commons-jelly_commons-jelly-tags-jsl-test.html
Work Name: build_commons-jelly_commons-jelly-tags-jsl-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 12 secs
Command Line: maven --offline jar 
[Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/jsl]
CLASSPATH: 
/usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/srv/gump/public/workspace/commons-cli-1.0.x/target/commons-cli-18072007.jar:/srv/gump/public/workspace/jakarta-commons/collections/build/commons-collections-18072007.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-18072007.jar:/srv/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-18072007.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-18072007.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar
-
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:64)
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:59)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:263)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187)
[junit] at 
org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:66)
[junit] at 
org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:113)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187)
[junit] at 
org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:161)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:80)
[junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:102)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:91)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:78)
[junit] at

[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed

2007-07-18 Thread commons-jelly-tags-jsl 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 [EMAIL PROTECTED]

Project commons-jelly-tags-jsl-test has an issue affecting its community 
integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-jsl-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on ant exists, no need to add for property 
maven.jar.ant-optional.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- (Gump generated) Maven Properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml
 -DEBUG- Maven project properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties
 -INFO- Project Reports in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/gump_work/build_commons-jelly_commons-jelly-tags-jsl-test.html
Work Name: build_commons-jelly_commons-jelly-tags-jsl-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 12 secs
Command Line: maven --offline jar 
[Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/jsl]
CLASSPATH: 
/usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/srv/gump/public/workspace/commons-cli-1.0.x/target/commons-cli-18072007.jar:/srv/gump/public/workspace/jakarta-commons/collections/build/commons-collections-18072007.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-18072007.jar:/srv/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-18072007.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-18072007.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar
-
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:64)
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:59)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:263)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187)
[junit] at 
org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:66)
[junit] at 
org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:113)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187)
[junit] at 
org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:161)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:80)
[junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:102)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:91)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:78)
[junit] at

[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) failed

2007-07-18 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 [EMAIL PROTECTED]

Project commons-jelly-tags-jaxme has an issue affecting its community 
integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-jaxme :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-jelly-tags-jaxme-18072007.jar] identifier set to 
project name
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme.
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme-js.
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme-xs.
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme-api.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- (Gump generated) Maven Properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/project.xml
 -DEBUG- Maven project properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/project.properties
 -INFO- Project Reports in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/target/test-reports
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/gump_work/build_commons-jelly_commons-jelly-tags-jaxme.html
Work Name: build_commons-jelly_commons-jelly-tags-jaxme (Type: Build)
Work ended in a state of : Failed
Elapsed: 10 secs
Command Line: maven --offline jar 
[Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme]
CLASSPATH: 
/usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/srv/gump/public/workspace/jakarta-commons/collections/build/commons-collections-18072007.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xmlunit/target/commons-jelly-tags-xmlunit-18072007.jar:/srv/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-18072007.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-18072007.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxme2-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmeapi-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmejs-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmexs-0.5.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/xmlunit/build/lib/xmlunit-18072007.jar
-
[javac] symbol  : variable super
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler
[javac]   super.characters(pChars, pOffset, pLen);
[javac]   ^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:305:
 cannot find symbol
[javac] symbol  : variable super
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler
[javac] super.init(pData);
[javac] ^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:315:
 cannot find symbol
[javac] symbol  : method getData()
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler
[javac] __handler_Name.init(getData());
[javac] ^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressHandler.java:22:
 cannot find symbol
[javac] symbol  : method getData()
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressHandler
[javac]   return

[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) failed

2007-07-18 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 [EMAIL PROTECTED]

Project commons-jelly-tags-jaxme has an issue affecting its community 
integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-jaxme :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-jelly-tags-jaxme-18072007.jar] identifier set to 
project name
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme.
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme-js.
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme-xs.
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme-api.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- (Gump generated) Maven Properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/project.xml
 -DEBUG- Maven project properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/project.properties
 -INFO- Project Reports in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/target/test-reports
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/gump_work/build_commons-jelly_commons-jelly-tags-jaxme.html
Work Name: build_commons-jelly_commons-jelly-tags-jaxme (Type: Build)
Work ended in a state of : Failed
Elapsed: 10 secs
Command Line: maven --offline jar 
[Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme]
CLASSPATH: 
/usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/srv/gump/public/workspace/jakarta-commons/collections/build/commons-collections-18072007.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-18072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xmlunit/target/commons-jelly-tags-xmlunit-18072007.jar:/srv/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-18072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-18072007.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-18072007.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxme2-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmeapi-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmejs-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmexs-0.5.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/xmlunit/build/lib/xmlunit-18072007.jar
-
[javac] symbol  : variable super
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler
[javac]   super.characters(pChars, pOffset, pLen);
[javac]   ^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:305:
 cannot find symbol
[javac] symbol  : variable super
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler
[javac] super.init(pData);
[javac] ^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:315:
 cannot find symbol
[javac] symbol  : method getData()
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler
[javac] __handler_Name.init(getData());
[javac] ^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressHandler.java:22:
 cannot find symbol
[javac] symbol  : method getData()
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressHandler
[javac]   return

[DBCP] More duplicate close JIRAs to close

2007-07-18 Thread Dain Sundstrom


I believe the duplicate close fix also addresses these JIRAs:

DBCP-5 PoolGuardConnectionWrapper violates close() contract
DBCP-23 SQLException When PoolablePreparedStatement Already Closed

-dain

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (DBCP-11) [dbcp] stmt.getConnection() != Connection used to create the statement

2007-07-18 Thread Dain Sundstrom (JIRA)


 [ 
https://issues.apache.org/jira/browse/DBCP-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dain Sundstrom updated DBCP-11:
---

Attachment: back-pointers.patch

This patch assures that all all returned Statements, PreparedStatements, 
CallableStatements and ResultSets are wrapped with a delegating object, which 
already properly handle the back pointers for Connection and Statement.  This 
patch includes an extensive test to assure that the *same* object used to 
create the statement or result set is returned from either the getConnection() 
or getStatementMethod().  


 [dbcp] stmt.getConnection() != Connection used to create the statement
 --

 Key: DBCP-11
 URL: https://issues.apache.org/jira/browse/DBCP-11
 Project: Commons Dbcp
  Issue Type: Bug
Affects Versions: 1.2
 Environment: Operating System: other
 Platform: All
Reporter: Alexander Rupsch
 Fix For: 1.3

 Attachments: back-pointers.patch


 Hi,
 I'm not an expert in implementing connection pools or jdbc itself. But 
 shouldn't
 the following code work?
 Connection con = pool.getConnection()
 PreparedStatement ps = con.prepareStatement()
 con.equals(ps.getConnection) // returns false!
 Ok, I don't need it to be equal, but the following also does not work:
 ps.getConnection().close()
 con.isClosed() // is false!!!
 That means, if I have a Statment and want to close its connection, I have to
 remember the conncetion. Is that the requested behavior? Because of this my 
 pool
 is running over.
 The java.sql API says that Statment.getConnection() has to be the connection
 which created the statement.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [DBCP] Back pointers

2007-07-18 Thread Dain Sundstrom


Sounds good to me.

I attached my fix to DBCP-11. This patch assures that all all  
returned Statements, PreparedStatements, CallableStatements and  
ResultSets are wrapped with a delegating object, which already  
properly handle the back pointers for Connection and Statement.  This  
patch includes an extensive test to assure that the *same* object  
used to create the statement or result set is returned from either  
the getConnection() or getStatementMethod().


Note we must make sure to update this test for each release of the  
JDBC spec we support as new ways of obtaining these objects tend to  
be added over time.


As per your suggestion below, this patch does not fix back pointers  
in connections obtained from a InstanceKeyDataSource using the  
cpdsadapter.  The cpdsadapter does not use the delegating wrapper  
internally, and will need a different solution.


DBCP-217 should also be closed.

-dain

On Jul 17, 2007, at 9:39 PM, Phil Steitz wrote:


On 7/17/07, Dain Sundstrom [EMAIL PROTECTED] wrote:

I'm working on a fix for the back pointers bugs DBCP-11 and DBCP-217
where the Statement.getConnection() and ResultSet.getStatement()
return the wrong objects.  The fix is pretty simple; we just need to
make sure we wrap Statements and ResultSets returned from
DelegatingConnection with the matching delegating type.


+1

Anyway, I

have the fix mostly complete with a bunch of test cases, but there is
one problem...

The PerUserPoolDataSource and SharedPoolDataSource classes return the
ConnectionImpl class directly.   This class is a wrapper around the
real connection so we need to wrap returned Statements which is easy
enough.  The problem is these datasources use the
CPDSConnectionFactory which does not call passivate on the delegating
connection when the connection is returned to the pool so the
Statements owned by the DelegatingConnection aren't closed.  To make
matters worse, CPDSConnectionFactory can't call passivate anyway
because it is in a different package and the method is protected :(

At this point I'm not sure what to do.  I could fix the problem for
all DataSources except for these two, and in the future we could
rework these two to subclass PoolingDataSource.  Alternative, we
could move CPDSConnectionFactory to same package as
DelegatingConnection or make is a sublcass of some ConnectionFactory
with access to the passivate method.

I really do think these datasources should be brought in line with
the main abstractions used by the other classes, but I don't think
that is something for this release (maybe for 2.0?).



I think we should leave this alone for now and consider refactoring
for 2.0, but there is a semantic difference that we need to keep in
mind.  InstanceKeyDataSource (parent of PerUser and SharedPool)
sources connections from a ConnectionPoolDataSource.  These
datasources return connection *handles* (PooledConnection impls),
which are not the same as DelegatingConnections. The cpdsadapter
package is just there for older jdbc drivers that do not provide
ConnectionPoolDataSource implementations.  See the javadoc for
InstanceKeyDataSource and also the implementation of makeObject there.
The key difference in the contract is that InstanceKeyDataSource
implements ConnectionEventListener, so when used with a driver that
correctly supports ConnectionPoolDataSource, the connection handles
handed out to users notify the pool (actually the factory in dbcp)
when they are closed by the user.  See connectionClosed in
CPDSConnectionFactory.

Phil

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r557381 - in /jakarta/commons/proper/jxpath/trunk/src/java/org/apache/commons/jxpath/ri: JXPathContextReferenceImpl.java model/VariablePointerFactory.java

2007-07-18 Thread mbenson

Author: mbenson
Date: Wed Jul 18 13:22:16 2007
New Revision: 557381

URL: http://svn.apache.org/viewvc?view=revrev=557381
Log:
[JXPATH-96] use NodePointerFactory for VariablePointers

Added:

jakarta/commons/proper/jxpath/trunk/src/java/org/apache/commons/jxpath/ri/model/VariablePointerFactory.java
   (with props)
Modified:

jakarta/commons/proper/jxpath/trunk/src/java/org/apache/commons/jxpath/ri/JXPathContextReferenceImpl.java

Modified: 
jakarta/commons/proper/jxpath/trunk/src/java/org/apache/commons/jxpath/ri/JXPathContextReferenceImpl.java
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/jxpath/trunk/src/java/org/apache/commons/jxpath/ri/JXPathContextReferenceImpl.java?view=diffrev=557381r1=557380r2=557381
==
--- 
jakarta/commons/proper/jxpath/trunk/src/java/org/apache/commons/jxpath/ri/JXPathContextReferenceImpl.java
 (original)
+++ 
jakarta/commons/proper/jxpath/trunk/src/java/org/apache/commons/jxpath/ri/JXPathContextReferenceImpl.java
 Wed Jul 18 13:22:16 2007
@@ -37,7 +37,6 @@
 import org.apache.commons.jxpath.JXPathNotFoundException;
 import org.apache.commons.jxpath.JXPathTypeConversionException;
 import org.apache.commons.jxpath.Pointer;
-import org.apache.commons.jxpath.Variables;
 import org.apache.commons.jxpath.ri.axes.InitialContext;
 import org.apache.commons.jxpath.ri.axes.RootContext;
 import org.apache.commons.jxpath.ri.compiler.Expression;
@@ -46,7 +45,7 @@
 import org.apache.commons.jxpath.ri.compiler.TreeCompiler;
 import org.apache.commons.jxpath.ri.model.NodePointer;
 import org.apache.commons.jxpath.ri.model.NodePointerFactory;
-import org.apache.commons.jxpath.ri.model.VariablePointer;
+import org.apache.commons.jxpath.ri.model.VariablePointerFactory;
 import org.apache.commons.jxpath.ri.model.beans.BeanPointerFactory;
 import org.apache.commons.jxpath.ri.model.beans.CollectionPointerFactory;
 import org.apache.commons.jxpath.ri.model.container.ContainerPointerFactory;
@@ -72,12 +71,13 @@
 private static Map compiled = new HashMap();
 private static int cleanupCount = 0;
 
-private static Vector nodeFactories = new Vector();
+private static final Vector nodeFactories = new Vector();
 private static NodePointerFactory nodeFactoryArray[] = null;
 static {
 nodeFactories.add(new CollectionPointerFactory());
 nodeFactories.add(new BeanPointerFactory());
 nodeFactories.add(new DynamicPointerFactory());
+nodeFactories.add(new VariablePointerFactory());
 
 // DOM  factory is only registered if DOM support is on the classpath
 Object domFactory = allocateConditionally(
@@ -618,26 +618,8 @@
 }
 
 public NodePointer getVariablePointer(QName name) {
-String varName = name.toString();
-JXPathContext varCtx = this;
-Variables vars = null;
-while (varCtx != null) {
-vars = varCtx.getVariables();
-if (vars.isDeclaredVariable(varName)) {
-break;
-}
-varCtx = varCtx.getParentContext();
-vars = null;
-}
-if (vars != null) {
-return new VariablePointer(vars, name);
-}
-else {
-// The variable is not declared, but we will create
-// a pointer anyway in case the user want to set, rather
-// than get, the value of the variable.
-return new VariablePointer(name);
-}
+return NodePointer.newNodePointer(name, VariablePointerFactory
+.contextWrapper(this), getLocale());
 }
 
 public Function getFunction(QName functionName, Object[] parameters) {

Added: 
jakarta/commons/proper/jxpath/trunk/src/java/org/apache/commons/jxpath/ri/model/VariablePointerFactory.java
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/jxpath/trunk/src/java/org/apache/commons/jxpath/ri/model/VariablePointerFactory.java?view=autorev=557381
==
--- 
jakarta/commons/proper/jxpath/trunk/src/java/org/apache/commons/jxpath/ri/model/VariablePointerFactory.java
 (added)
+++ 
jakarta/commons/proper/jxpath/trunk/src/java/org/apache/commons/jxpath/ri/model/VariablePointerFactory.java
 Wed Jul 18 13:22:16 2007
@@ -0,0 +1,99 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the License); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an AS IS BASIS,
+ * WITHOUT

[jira] Resolved: (JXPATH-96) Extract VariablePointerFactory interface

2007-07-18 Thread Matt Benson (JIRA)


 [ 
https://issues.apache.org/jira/browse/JXPATH-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Benson resolved JXPATH-96.
---

Resolution: Fixed

There are many reasons this could not be implemented as requested.  You have 
placed dependencies in JXPathContext upon NodePointer, etc., from the reference 
implementation.  What I have done is change the RI such that it delegates the 
creation of variable pointers to the registered NodePointerFactories as it does 
with the other various nodes in a given graph, wrapping the context itself in a 
type that the new VariablePointerFactory NodePointerFactory implementation 
recognizes.  Now you will extend the RI in much the same way as you would any 
other time you needed to add a custom NodePointerFactory, except that you will 
trigger your VariablePointerFactory, or replacement thereof, on the 
VariablePointerFactory.VariableContextWrapper bean type.  Since the default 
implementation is now being used for the creation of VariablePointers the 
existing testcases validate that this functionality is working properly.

Best,
Matt

 Extract VariablePointerFactory interface
 

 Key: JXPATH-96
 URL: https://issues.apache.org/jira/browse/JXPATH-96
 Project: Commons JXPath
  Issue Type: New Feature
Affects Versions: 1.2 Final
Reporter: Sergey Vladimirov
Assignee: Matt Benson
 Fix For: 1.3

 Attachments: patch.txt, VariablePointerFactoryTest.java


 Extract VariablePointerFactory interface from JXPathContextReferenceImpl, and 
 pull up using of it to JXPathContext

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r557397 - in /jakarta/commons/proper/digester/trunk: build.properties.sample build.xml

Author: bayard
Date: Wed Jul 18 14:11:26 2007
New Revision: 557397

URL: http://svn.apache.org/viewvc?view=revrev=557397
Log:
The build.xml is simplified, using an include/exclude approach with the junit 
task rather than defining a task per test package. The build.properties.sample 
is updated to look in the local .maven by default, making it easier for the 
average committer to test the ant build out. See: DIGESTER-117

Modified:
jakarta/commons/proper/digester/trunk/build.properties.sample
jakarta/commons/proper/digester/trunk/build.xml

Modified: jakarta/commons/proper/digester/trunk/build.properties.sample
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/digester/trunk/build.properties.sample?view=diffrev=557397r1=557396r2=557397
==
--- jakarta/commons/proper/digester/trunk/build.properties.sample (original)
+++ jakarta/commons/proper/digester/trunk/build.properties.sample Wed Jul 18 
14:11:26 2007
@@ -1,57 +1,56 @@
-#
-# Ant configuration file
-#
-# When building Digester using Ant it is necessary to provide Ant with
-# some configuration information about the setup of the host machine on
-# which the build is happening. 
+#   Licensed to the Apache Software Foundation (ASF) under one or more
+#   contributor license agreements.  See the NOTICE file distributed with
+#   this work for additional information regarding copyright ownership.
+#   The ASF licenses this file to You under the Apache License, Version 2.0
+#   (the License); you may not use this file except in compliance with
+#   the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+#   Unless required by applicable law or agreed to in writing, software
+#   distributed under the License is distributed on an AS IS BASIS,
+#   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+#   See the License for the specific language governing permissions and
+#   limitations under the License.
+
+##
+# Sample Ant build.properties file
+#
+# This setup assumes dependent jars are in a local maven 1 repository.
+# However the jars are located, the properties ending in .jar need
+# expand to full paths to the jars.
 #
 # Copy this file (build.properties.sample) to build.properties then edit
 # entries below as appropriate before running any Ant commands.
-#
-#
+##
 
-# Specify a base directory where required jar files can be found.
-# Alternatively, provide complete paths to all of the needed libaries below.
+# Repository base path
+repository=${user.home}/.maven/repository
 
-root=/java/jars
+# JUnit
+junit.home=${repository}/junit/jars
+junit.jar=${junit.home}/junit-3.8.1.jar
 
+# XML parser
 # When using java 1.3 or earlier, JAXP is not included in the standard
 # libraries, so external jar files are required. If you are using Java
 # 1.4 or later, you can omit these libraries
-#
-# Note that when using xerces parser, the bundled xml-apis.jar provides the
-# same classes as Sun's jaxp.jar.
-
-jaxp.home=${root}
-jaxp.jaxp.jar=${jaxp.home}/jaxp.jar
-jaxp.parser.jar=${jaxp.home}/crimson.jar
-
-# Digester depends upon several other commons projects. 
-#
-# If you are building Digester from a checkout of the trunks-proper directory
-# and have already built the latest code for each of the dependent projects 
-# then these paths are automatically correct. 
-#
-# In other circumstances, provide direct paths (possibly based on ${root}
-# to all these required libraries.
-#
-# Note that Digester no longer depends on commons-collections itself; there is
-# a runtime dependency currently inherited from commons-beanutils, however.
-#
-# See file project.xml or RELEASE-NOTES.txt for the specific versions of these
-# files which are required.
-
-commons-beanutils.home=../beanutils/dist
-commons-beanutils.jar=${commons-beanutils.home}/commons-beanutils.jar
-commons-logging.home=../logging/dist
-commons-logging.jar=${commons-logging.home}/commons-logging.jar
-
-# JUnit is required if compiling/running the unit tests
-
-junit.jar=${root}/junit.jar
+jaxp.parser.home=${repository}/xerces/jars
+jaxp.parser.jar=${jaxp.parser.home}/xerces-2.0.2.jar
+jaxp.jaxp.home=${repository}/xml-apis/jars
+jaxp.jaxp.jar=${jaxp.jaxp.home}/xml-apis-1.0.b2.jar
+
+# Commons logging
+commons-logging.home=${repository}/commons-logging/jars
+commons-logging.jar=${commons-logging.home}/commons-logging-1.1.jar
+
+# Commons beanutils
+commons-beanutils.home=${repository}/commons-beanutils/jars
+commons-beanutils.jar=${commons-beanutils.home}/commons-beanutils-1.7.0.jar
 
 # The digester tests output logging information (including Exceptions)

[jira] Commented: (DIGESTER-115) Digester depends on BeanUtils copies of Collections classes


[ 
https://issues.apache.org/jira/browse/DIGESTER-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513723
 ] 

Henri Yandell commented on DIGESTER-115:


Note, it only directly depends on ArrayStack. Buffer and 
BufferUnderflowException are depended on via ArrayStack.

A tighter ArrayStack could definitely be made (remove the unnecessary bits) and 
used within Digester.

 Digester depends on BeanUtils copies of Collections classes
 ---

 Key: DIGESTER-115
 URL: https://issues.apache.org/jira/browse/DIGESTER-115
 Project: Commons Digester
  Issue Type: Bug
Affects Versions: 1.8
Reporter: Niall Pemberton
 Fix For: 1.8.1


 This is related to issue# BEANUTILS-278
 Digester uses 3 classes (ArrayStack, Buffer and BufferUnderflowException) 
 from commons BeanUtils which were copied from Commons Collections and 
 BEANUTILS-278 proposes removing them.
 ArrayStack.java
 Buffer.java
 BufferUnderflowException.java

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (DIGESTER-115) Digester depends on BeanUtils copies of Collections classes


 [ 
https://issues.apache.org/jira/browse/DIGESTER-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated DIGESTER-115:
---

Fix Version/s: 1.8.1

 Digester depends on BeanUtils copies of Collections classes
 ---

 Key: DIGESTER-115
 URL: https://issues.apache.org/jira/browse/DIGESTER-115
 Project: Commons Digester
  Issue Type: Bug
Affects Versions: 1.8
Reporter: Niall Pemberton
 Fix For: 1.8.1


 This is related to issue# BEANUTILS-278
 Digester uses 3 classes (ArrayStack, Buffer and BufferUnderflowException) 
 from commons BeanUtils which were copied from Commons Collections and 
 BEANUTILS-278 proposes removing them.
 ArrayStack.java
 Buffer.java
 BufferUnderflowException.java

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (DIGESTER-114) SetPropertyRule throws /java.lang.IllegalArgumentException: No name specified/ when matched element has no attributes


 [ 
https://issues.apache.org/jira/browse/DIGESTER-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated DIGESTER-114:
---

Fix Version/s: 1.8.1

 SetPropertyRule throws /java.lang.IllegalArgumentException: No name 
 specified/ when matched element has no attributes
 -

 Key: DIGESTER-114
 URL: https://issues.apache.org/jira/browse/DIGESTER-114
 Project: Commons Digester
  Issue Type: Bug
Affects Versions: 1.8
Reporter: Britt Levy
 Fix For: 1.8.1


 A /java.lang.IllegalArgumentException: No name specified/ is thrown from the 
 SetPropertyRule.begin(Attributes attributes) method if the attributes list is 
 empty (attributes.getLength() = 0). The method should check the length of the 
 attributes list and simply return if there are no attributes.
 Add the follwowing to org.apache.commons.digester.SetPropertyRuleTestCase to 
 reproduce:
 /**
  * Simple test xml document used in the tests.
  */
 protected final static String TEST_XML_3 =
 ?xml version='1.0'?root +
 set/ +
 /root;
  /**
  * Test SetPropertyRule when matched XML element has no attributes.
  */
 public void testElementWithNoAttributes() throws Exception {
 // Set up the rules we need
 digester.addObjectCreate(root,
  
 org.apache.commons.digester.SimpleTestBean);
 digester.addSetProperty(root/set, name, value);
 // Parse the input - should not throw an exception
 SimpleTestBean bean =
 (SimpleTestBean) digester.parse(xmlTestReader(TEST_XML_3));
   }   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (DIGESTER-109) FromXmlRuleSet and SetNextRule classloader issue


 [ 
https://issues.apache.org/jira/browse/DIGESTER-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell closed DIGESTER-109.
--

Resolution: Won't Fix

Closing as WONTFIX, as with the validator issue this links to.

The workaround is to call Digester.setUseContextClassLoader(true).

 FromXmlRuleSet  and  SetNextRule  classloader issue
 ---

 Key: DIGESTER-109
 URL: https://issues.apache.org/jira/browse/DIGESTER-109
 Project: Commons Digester
  Issue Type: Bug
Reporter: Anna Komaristaia

 When I start the application in Unix, there are 2 classes cause the problem:
 1)  The NullPointerException in FromXmlRuleSet   class in the method 
 addRuleInstances(Digester, String);
 2)  The NullPointerException in SetNextRule class in the method end();
 Temporary solution
 ---
  I recompiled the commons-digester jar with the next changes and it's working 
 fine in PC and Unix: 
 Changes in the FromXmlRuleSet   class 
   
 1)  public static final String DIGESTER_DTD_PATH = digester-rules.dtd;
 2)  in the method addRuleInstances  
   the line 
  URL dtdURL = 
 getClass().getClassLoader().getResource(DIGESTER_DTD_PATH);
 
  changed by
 
  URL dtdURL = this.getClass().getResource(DIGESTER_DTD_PATH); 
 Changes In the SetNextRule class 
 the line
  paramTypes[0] = digester.getClassLoader().loadClass( 
 paramType);
changed by
   if( digester.getClassLoader() == null )
 paramTypes[0] = Class.forName(paramType);
   else
 paramTypes[0] = digester.getClassLoader().loadClass( 
 paramType);
 Thanks, 
 //Anna 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r557404 - /jakarta/commons/proper/digester/trunk/build.xml

Author: bayard
Date: Wed Jul 18 14:37:11 2007
New Revision: 557404

URL: http://svn.apache.org/viewvc?view=revrev=557404
Log:
Applying Petteri Ra:ty's build.xml improvement from DIGESTER-89 so you can 
build the jar without the javadoc. I did modify it so you are forced to run the 
tests when building the jar

Modified:
jakarta/commons/proper/digester/trunk/build.xml

Modified: jakarta/commons/proper/digester/trunk/build.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/digester/trunk/build.xml?view=diffrev=557404r1=557403r2=557404
==
--- jakarta/commons/proper/digester/trunk/build.xml (original)
+++ jakarta/commons/proper/digester/trunk/build.xml Wed Jul 18 14:37:11 2007
@@ -256,20 +256,22 @@
 /javadoc
   /target
 
+  target name=jar depends=compile, test
+   description=Create commons-digester.jar
+mkdir  dir=${dist.home}/
+jarjarfile=${dist.home}/commons-${component.name}.jar
+basedir=${build.home}/classes
+   manifest=${build.home}/conf/MANIFEST.MF/
+  /target
 
-  target name=dist depends=compile,javadoc
+  target name=dist depends=jar,javadoc
description=Create binary distribution
-mkdir  dir=${dist.home}/
 copy  file=LICENSE.txt
   todir=${dist.home}/
-mkdir  dir=${build.home}/classes/META-INF/
 copy  file=RELEASE-NOTES.txt
   todir=${dist.home}/
 copy  file=NOTICE.txt
   todir=${dist.home}/
-jarjarfile=${dist.home}/commons-${component.name}.jar
-basedir=${build.home}/classes
-   manifest=${build.home}/conf/MANIFEST.MF/
   /target
 
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (DIGESTER-89) [digester] [PATCH] add jar target to build.xml


 [ 
https://issues.apache.org/jira/browse/DIGESTER-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell closed DIGESTER-89.
-

   Resolution: Fixed
Fix Version/s: 1.8.1

svn ci -m Applying Petteri Räty's build.xml improvement from DIGESTER-89 so 
you can build the jar without the javadoc. I did modify it so you are forced to 
run the tests when building the jar build.xml

Sendingbuild.xml
Transmitting file data .
Committed revision 557404.

Thanks Petteri.

 [digester] [PATCH] add jar target to build.xml
 --

 Key: DIGESTER-89
 URL: https://issues.apache.org/jira/browse/DIGESTER-89
 Project: Commons Digester
  Issue Type: Improvement
 Environment: Operating System: All
 Platform: Other
Reporter: Petteri Räty
Priority: Minor
 Fix For: 1.8.1

 Attachments: 1.7-build.xml-jar-target.patch


 Now to create the commons-digester.jar file one must also create javadocs. 
 Here
 is a patch that add a jar target so I don't need to run javadoc to create the
 jar file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (DIGESTER-117) Missing unit tests using ant and maven

[
https://issues.apache.org/jira/browse/DIGESTER-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Henri Yandell closed DIGESTER-117.
--

Resolution: Fixed
Fix Version/s: 1.8.1

Emulating the changes in DBCP/Beanutils (I think it was those two); I've opted
to update the build.xml and not to use 'maven ant'.

I've also rewritten the build.properties.sample, using dbcp's as an example, so
that running 'maven jar' puts the various required jar files into the location
expected by the sample.

Missing unit tests using ant and maven
--

Key: DIGESTER-117
URL: https://issues.apache.org/jira/browse/DIGESTER-117
Project: Commons Digester
Issue Type: Bug
Affects Versions: 1.8
Reporter: Gail Badner
Fix For: 1.8.1

Currently, 136 unit tests are run using maven and 149 unit tests are run
using ant.
The maven build uses the file patterns:
**/*Test.java
**/*TestCase.java
which misses the following tests:
**/plugins/TestAll.java
**/TestFactoryCreate.java
After the missing tests are added to the maven build, 157 tests are executed.
The ant build does not execute the following tests:
LocationTrackerTestCase
NamespaceSnapshotTestCase
OverlappingCallMethodRuleTestCase
After the missing tests to the ant build, 157 tests are executed.
I'm not sure how this should be fixed; should test cases that don't end in
Test or TestCase be renamed?
When this is fixed, it would be nice if the junit ant task were used to run
the tests so that the JUnit report can be generated.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (DIGESTER-111) Null InputStream leads to MalformedURLExceptions under JDK 1.5


 [ 
https://issues.apache.org/jira/browse/DIGESTER-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated DIGESTER-111:
---

Fix Version/s: 1.8.1

 Null InputStream leads to MalformedURLExceptions under JDK 1.5
 --

 Key: DIGESTER-111
 URL: https://issues.apache.org/jira/browse/DIGESTER-111
 Project: Commons Digester
  Issue Type: Improvement
Affects Versions: 1.8
Reporter: Niall Pemberton
Priority: Minor
 Fix For: 1.8.1


 Passing a null InputStream to Digester.parse(InputStream) causes a confusing 
 java.net.MalformedURLException under JDK 1.5
 Would be more user friendly to trap this condition and throw an appropriate 
 exception and message.
 This came up as an issue in Commons Validator - see VALIDATOR-226

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (LANG-349) Deadlock using ReflectionToStringBuilder


 [ 
https://issues.apache.org/jira/browse/LANG-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated LANG-349:
---

Fix Version/s: 2.3.1

First step - attempt a reproduction. If that fails, then dig into the code and 
see if it's obvious.

 Deadlock using ReflectionToStringBuilder
 

 Key: LANG-349
 URL: https://issues.apache.org/jira/browse/LANG-349
 Project: Commons Lang
  Issue Type: Bug
Affects Versions: 2.0
 Environment: java version 1.5.0_10
 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
 Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
 uname -a
 Linux fwjsfimat04 2.4.21-32.EL #1 SMP Fri Apr 15 21:02:58 EDT 2005 x86_64 
 x86_64 x86_64 GNU/Linux
Reporter: David I.
Priority: Critical
 Fix For: 2.3.1


 I used the ReflectionToStringBuilder on an object to output debugging 
 messages to Log4j. If this object was picked up by two different threads and 
 the toString() method was called at the same time in two different threads, a 
 deadlock occurrs.
 Here is a stack trace from using jstack:
 Thread 1172: (state = BLOCKED)
  - java.util.Vector.hashCode() @bci=0, line=938 (Interpreted frame)
  - java.util.HashMap.containsKey(java.lang.Object) @bci=6, line=377 (Compiled 
 frame)
  - org.apache.commons.lang.builder.ReflectionToStringBuilder.toString() 
 @bci=50, line=522 (Compiled frame)
  - 
 org.apache.commons.lang.builder.ReflectionToStringBuilder.toString(java.lang.Object,
  org.apache.commons.lang.builder.ToStringStyle, boolean, java.lang.Class) 
 @bci=12, line=265 (Interpreted frame)
  - 
 org.apache.commons.lang.builder.ReflectionToStringBuilder.toString(java.lang.Object,
  org.apache.commons.lang.builder.ToStringStyle) @bci=4, line=197 (Interpreted 
 frame)
  - 
 org.apache.commons.lang.builder.ToStringBuilder.reflectionToString(java.lang.Object,
  org.apache.commons.lang.builder.ToStringStyle) @bci=2, line=170 (Interpreted 
 frame)
 [...]
 Thread 1191: (state = BLOCKED)
  - java.util.Vector.hashCode() @bci=0, line=938 (Interpreted frame)
  - java.util.HashMap.containsKey(java.lang.Object) @bci=6, line=377 (Compiled 
 frame)
  - org.apache.commons.lang.builder.ReflectionToStringBuilder.toString() 
 @bci=50, line=522 (Compiled frame)
  [...]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r557415 - /jakarta/commons/proper/daemon/trunk/src/java/org/apache/commons/daemon/Daemon.java

Author: bayard
Date: Wed Jul 18 15:15:21 2007
New Revision: 557415

URL: http://svn.apache.org/viewvc?view=revrev=557415
Log:
Fixing 'avfter' to 'after' typo as per DAEMON-101

Modified:

jakarta/commons/proper/daemon/trunk/src/java/org/apache/commons/daemon/Daemon.java

Modified: 
jakarta/commons/proper/daemon/trunk/src/java/org/apache/commons/daemon/Daemon.java
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/daemon/trunk/src/java/org/apache/commons/daemon/Daemon.java?view=diffrev=557415r1=557414r2=557415
==
--- 
jakarta/commons/proper/daemon/trunk/src/java/org/apache/commons/daemon/Daemon.java
 (original)
+++ 
jakarta/commons/proper/daemon/trunk/src/java/org/apache/commons/daemon/Daemon.java
 Wed Jul 18 15:15:21 2007
@@ -75,7 +75,7 @@
  * method has been successfully invoked and possibly the security
  * level of the JVM has been dropped.  codeImplementors of this
  * method are free to start any number of threads, but need to
- * return control avfter having done that to enable invocation of
+ * return control after having done that to enable invocation of
  * the stop()-method.
  */
 public void start()



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r557416 - /jakarta/commons/proper/daemon/trunk/src/java/org/apache/commons/daemon/Daemon.java

Author: bayard
Date: Wed Jul 18 15:16:26 2007
New Revision: 557416

URL: http://svn.apache.org/viewvc?view=revrev=557416
Log:
Also removing unnecessary code tag as per DAEMON-101

Modified:

jakarta/commons/proper/daemon/trunk/src/java/org/apache/commons/daemon/Daemon.java

Modified: 
jakarta/commons/proper/daemon/trunk/src/java/org/apache/commons/daemon/Daemon.java
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/daemon/trunk/src/java/org/apache/commons/daemon/Daemon.java?view=diffrev=557416r1=557415r2=557416
==
--- 
jakarta/commons/proper/daemon/trunk/src/java/org/apache/commons/daemon/Daemon.java
 (original)
+++ 
jakarta/commons/proper/daemon/trunk/src/java/org/apache/commons/daemon/Daemon.java
 Wed Jul 18 15:16:26 2007
@@ -73,7 +73,7 @@
  * Start the operation of this codeDaemon/code instance. This
  * method is to be invoked by the environment after the init()
  * method has been successfully invoked and possibly the security
- * level of the JVM has been dropped.  codeImplementors of this
+ * level of the JVM has been dropped. Implementors of this
  * method are free to start any number of threads, but need to
  * return control after having done that to enable invocation of
  * the stop()-method.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (DAEMON-101) Javadoc typo, says avfter should probably be after


 [ 
https://issues.apache.org/jira/browse/DAEMON-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell closed DAEMON-101.


Resolution: Fixed

Thanks Tim, both have been fixed in SVN.

 Javadoc typo, says avfter should probably be after
 --

 Key: DAEMON-101
 URL: https://issues.apache.org/jira/browse/DAEMON-101
 Project: Commons Daemon
  Issue Type: Improvement
 Environment: N/A, javadoc
Reporter: Tim Mooney
Priority: Trivial

 Javadoc for the Daemon interface method start uses the word avfter, should 
 probably be after.  The comment may also fail to close a code tag (which 
 doesn't seem to be valid, anyway).
 Full comment:
 Start the operation of this Daemon instance. This method is to be invoked by 
 the environment after the init() method has been successfully invoked and 
 possibly the security level of the JVM has been dropped. Implementors of this 
 method are free to start any number of threads, but need to return control 
 avfter having done that to enable invocation of the stop()-method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

IE7 and Apache Common File Upload

2007-07-18 Thread redomancer redomancer


Hello!
I am not sure i am posting the questions in right place, but i have no other
option.

I have problem witch is related to Apache Common File Upload.

First of all - the code I am using for file saving:

//
   FileItemIterator anIterator = (new
ServletFileUpload()).getItemIterator(aRequest);
   FileItemStream anItem = null;
   InputStream aInputStream = null;
   while (anIterator.hasNext()) {
   anItem = anIterator.next();
   aInputStream = anItem.openStream();
   if (anItem.isFormField())
   // ... form field
   else {
   BufferedInputStream aBufferedInputStream = new
BufferedInputStream(aInputStream);
   OutputStream aOutputStream = new
FileOutputStream(getRealPath() + anItem.getName());
   BufferedOutputStream aBufferedOutputStream = new
BufferedOutputStream(aOutputStream);
   int aStreamedDataSize = 0;
   while((aStreamedDataSize =
aBufferedInputStream.read())!=-1)
{
   aBufferedOutputStream.write(aStreamedDataSize);
   }
   aBufferedOutputStream.flush();
   aBufferedOutputStream.close();
   aBufferedInputStream.close();
   aOutputStream.flush();
   aOutputStream.close();
   }
   }
//

getRealPath() is my function what returns the directory where file must be
saved.

And now the problem: anItem.getName() for IE7 returns FULL path to file on
client side machine.
For example: if i had file C:\upload_me.txt, then anItem.getName() will
contain C:\upload_me.txt if IE7 submits data;
for other browsers anItem.getName() will contail value upload_me.txt.

Is it supposed to be so?
What data anItem.getName() must return? And what is the correct way to get
file name for all browsers then?

P.S.
Sorry, if my question is silly.


redo

[jira] Commented: (JXPATH-96) Extract VariablePointerFactory interface

2007-07-18 Thread Sergey Vladimirov (JIRA)


[ 
https://issues.apache.org/jira/browse/JXPATH-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513743
 ] 

Sergey Vladimirov commented on JXPATH-96:
-

It will be nice to add test case to SVN as well
As an example for me :)

 Extract VariablePointerFactory interface
 

 Key: JXPATH-96
 URL: https://issues.apache.org/jira/browse/JXPATH-96
 Project: Commons JXPath
  Issue Type: New Feature
Affects Versions: 1.2 Final
Reporter: Sergey Vladimirov
Assignee: Matt Benson
 Fix For: 1.3

 Attachments: patch.txt, VariablePointerFactoryTest.java


 Extract VariablePointerFactory interface from JXPathContextReferenceImpl, and 
 pull up using of it to JXPathContext

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: IE7 and Apache Common File Upload

2007-07-18 Thread Martin Cooper


On 7/18/07, redomancer redomancer [EMAIL PROTECTED] wrote:


Hello!
I am not sure i am posting the questions in right place, but i have no
other
option.



Um, yes, you do - the Commons User list is the place for questions like
this. Nevertheless, the answer to your question is in the FileUpload FAQ:

http://jakarta.apache.org/commons/fileupload/faq.html#whole-path-from-IE

--
Martin Cooper


I have problem witch is related to Apache Common File Upload.


First of all - the code I am using for file saving:

//
FileItemIterator anIterator = (new
ServletFileUpload()).getItemIterator(aRequest);
FileItemStream anItem = null;
InputStream aInputStream = null;
while (anIterator.hasNext()) {
anItem = anIterator.next();
aInputStream = anItem.openStream();
if (anItem.isFormField())
// ... form field
else {
BufferedInputStream aBufferedInputStream = new
BufferedInputStream(aInputStream);
OutputStream aOutputStream = new
FileOutputStream(getRealPath() + anItem.getName());
BufferedOutputStream aBufferedOutputStream = new
BufferedOutputStream(aOutputStream);
int aStreamedDataSize = 0;
while((aStreamedDataSize =
aBufferedInputStream.read())!=-1)
{
aBufferedOutputStream.write
(aStreamedDataSize);
}
aBufferedOutputStream.flush();
aBufferedOutputStream.close();
aBufferedInputStream.close();
aOutputStream.flush();
aOutputStream.close();
}
}
//

getRealPath() is my function what returns the directory where file must be
saved.

And now the problem: anItem.getName() for IE7 returns FULL path to file on
client side machine.
For example: if i had file C:\upload_me.txt, then anItem.getName() will
contain C:\upload_me.txt if IE7 submits data;
for other browsers anItem.getName() will contail value upload_me.txt.

Is it supposed to be so?
What data anItem.getName() must return? And what is the correct way to get
file name for all browsers then?

P.S.
Sorry, if my question is silly.


redo

svn commit: r557435 - in /jakarta/commons/proper/collections/branches/collections_jdk5_branch/src/test/org/apache/commons/collections: bag/AbstractTestBag.java list/AbstractTestList.java

2007-07-18 Thread skestle

Author: skestle
Date: Wed Jul 18 17:35:50 2007
New Revision: 557435

URL: http://svn.apache.org/viewvc?view=revrev=557435
Log:
Skipped failing SerializedCanonicalTests.  Marked code to be revisited through 
collections re-work.

Modified:

jakarta/commons/proper/collections/branches/collections_jdk5_branch/src/test/org/apache/commons/collections/bag/AbstractTestBag.java

jakarta/commons/proper/collections/branches/collections_jdk5_branch/src/test/org/apache/commons/collections/list/AbstractTestList.java

Modified: 
jakarta/commons/proper/collections/branches/collections_jdk5_branch/src/test/org/apache/commons/collections/bag/AbstractTestBag.java
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/collections/branches/collections_jdk5_branch/src/test/org/apache/commons/collections/bag/AbstractTestBag.java?view=diffrev=557435r1=557434r2=557435
==
--- 
jakarta/commons/proper/collections/branches/collections_jdk5_branch/src/test/org/apache/commons/collections/bag/AbstractTestBag.java
 (original)
+++ 
jakarta/commons/proper/collections/branches/collections_jdk5_branch/src/test/org/apache/commons/collections/bag/AbstractTestBag.java
 Wed Jul 18 17:35:50 2007
@@ -474,6 +474,17 @@
 }
 
 /**
+ * Skip the serialized cannonical tests for now.
+ *
+ * @return true
+ *
+ * TODO: store a new serialized object on the disk.
+ */
+protected boolean skipSerializedCanonicalTests() {
+return true;
+}
+
+/**
  * Compare the current serialized form of the Bag
  * against the canonical version in CVS.
  */

Modified: 
jakarta/commons/proper/collections/branches/collections_jdk5_branch/src/test/org/apache/commons/collections/list/AbstractTestList.java
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/collections/branches/collections_jdk5_branch/src/test/org/apache/commons/collections/list/AbstractTestList.java?view=diffrev=557435r1=557434r2=557435
==
--- 
jakarta/commons/proper/collections/branches/collections_jdk5_branch/src/test/org/apache/commons/collections/list/AbstractTestList.java
 (original)
+++ 
jakarta/commons/proper/collections/branches/collections_jdk5_branch/src/test/org/apache/commons/collections/list/AbstractTestList.java
 Wed Jul 18 17:35:50 2007
@@ -1055,6 +1055,17 @@
 }
 
 /**
+ * Skip the serialized canonical tests for now.
+ *
+ * @return true
+ *
+ * TODO: store new serialized objects in CVS.
+ */
+protected boolean skipSerializedCanonicalTests() {
+return true;
+}
+
+/**
  * Compare the current serialized form of the List
  * against the canonical version in CVS.
  */



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (DBCP-5) [dbcp] PoolGuardConnectionWrapper violates close() contract


 [ 
https://issues.apache.org/jira/browse/DBCP-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Phil Steitz resolved DBCP-5.


Resolution: Fixed

Fixed in r 557176.

 [dbcp] PoolGuardConnectionWrapper violates close() contract
 ---

 Key: DBCP-5
 URL: https://issues.apache.org/jira/browse/DBCP-5
 Project: Commons Dbcp
  Issue Type: Bug
 Environment: Operating System: All
 Platform: All
Reporter: Derek Park
 Fix For: 1.3


 org.apache.commons.dbcp.PoolingDatasource.PoolGuardConnectionWrapper.close()
 violates the Connection.close() contract specified in the Java 1.5 API.  The
 current API specifies that calling close() on an already-closed connection is 
 a
 no-op.  (Blame Sun for the bug.  The API didn't used to say that.)  
 PoolGuardConnectionWrapper.close() first calls checkOpen() which throws an
 exception if close() has already been called.  Clearly that's not a no-op.
 The simplest fix is to change the first line in the close() method from this:
 checkOpen();
 to this:
 if (this.delegate == null) return;
 As of today (2006-03-22) this bug is in the latest SVN source (and has been in
 previous versions as well).
 DelegatingConnection and PoolingConnection don't seem (from a quick glance) to
 have this problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (DBCP-23) [dbcp] SQLException When PoolablePreparedStatement Already Closed


 [ 
https://issues.apache.org/jira/browse/DBCP-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Phil Steitz resolved DBCP-23.
-

Resolution: Fixed

Fixed in r 557176.

 [dbcp] SQLException When PoolablePreparedStatement Already Closed
 -

 Key: DBCP-23
 URL: https://issues.apache.org/jira/browse/DBCP-23
 Project: Commons Dbcp
  Issue Type: Bug
Affects Versions: 1.2
 Environment: Operating System: All
 Platform: All
Reporter: JZ
 Fix For: 1.3

 Attachments: issue32441.patch, patch.txt


 When closing an already closed
 org.apache.commons.dbcp.PoolablePreparedStatement, a SQLException is thrown 
 when
 the isClosed() method returns true.
 This seems to violate the contract of java.sql.Statement (super interface of
 implemented PreparedStatement) whose javadoc reads  Calling the method close 
 on
 a Statement  object that is already closed has no effect. 
 Work around exists -- when ever closing a statement, also null out.  Then,
 before closing, check that it's non-null.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r557488 - /jakarta/commons/proper/dbcp/trunk/xdocs/changes.xml