Re: [BeanUtils] Progressing towards a 1.8.0 release
On 7/19/07, Stephen Colebourne [EMAIL PROTECTED] wrote: But surely, the problem is that maven will pull in collections.jar when it pulls in beanutils.jar, which is unnecessary. Its big, unnecessary dependencies like this that give commons a bad name. Do you know, that you can exclude transitive dependencies when you specify a direct dependency? -- Besides, manipulating elections is under penalty of law, resulting in a preventative effect against manipulating elections. The german government justifying the use of electronic voting machines and obviously believing that we don't need a police, because all illegal actions are forbidden. http://dip.bundestag.de/btd/16/051/1605194.pdf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [BeanUtils] Progressing towards a 1.8.0 release
Henri Yandell wrote: On 7/17/07, Niall Pemberton [EMAIL PROTECTED] wrote: Assemblies work except you only get a default manifest - not sure where I got the attachment idea from, can't find any reference to that - so I think we should keep it simple and stick to option #1 That has my +1 [obviously]. I think we should keep it simple. But surely, the problem is that maven will pull in collections.jar when it pulls in beanutils.jar, which is unnecessary. Its big, unnecessary dependencies like this that give commons a bad name. Anyway, I'll not block this, if this is the way you want to go. Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TRANSACTION-9) [transaction] Add full file management capabilities to the FileResourceManager
[ https://issues.apache.org/jira/browse/TRANSACTION-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513844 ] Oliver Zeigermann commented on TRANSACTION-9: - Yes. Something like a select for update right? This could also be a means to reduce deadlock hazards. unlock() certainly is not needed and even dangerous as no locks must not be released before the end of the transaction to ensure serializability. OK. What about that: public interface Resource { String getPath(); boolean isDirectory(); boolean isFile(); CollectionResource getChildren() throws IOException, LockException; InputStream readStream() throws IOException, LockException; OutputStream writeStream() throws IOException, LockException; boolean delete() throws IOException, LockException; boolean move(String destinationpath) throws IOException, LockException; boolean copy(String destinationpath) throws IOException, LockException; // plus more general properties // among them could be length, lastmodfied, etc. MapString, Property getProperties(); void setProperties(MapString, Property newProperties); // plus locking methods void readLock(); void writeLock(); boolean tryReadLock(); boolean tryWriteLock(); } public interface Property { String getName(); Object getValue(); Object setValue(Object newValue); Class getType(); } Is that better? Still anything missing? [transaction] Add full file management capabilities to the FileResourceManager -- Key: TRANSACTION-9 URL: https://issues.apache.org/jira/browse/TRANSACTION-9 Project: Commons Transaction Issue Type: Improvement Environment: Operating System: All Platform: All Reporter: Peter Fassev Assignee: Oliver Zeigermann Priority: Minor Fix For: 2.0 Attachments: filemanager.zip Hi, As stated in the doc the FileResourceManager is: A resource manager for streamable objects stored in a file system I agree, that this is a resource manager, but it could be easily extended, to support a full file management system. It will be very helpful to have additional methods like renameResource(), getResourceSize(), getResourceTime(), setResourceTime() etc. This are common file operations, which should be managed by the FileResourceManager. Further it will be very helpful to have (real) support for resource collections (folders). It will be necessary to distinguish between single resources (files) and collections (folders). Together, this features will enable a transactional access to any file based resources - for instance a document repository. Are there plans for such extensions and if not, will they actually fit in the goals of the transaction library? If not, please open the underlying structure, like the inner class TransactionContext, in order to add extensions the file management. For instance, it will be good to have a separate factory method, which creates the context. If you are interested in this proposal, I am ready to contribute to this project. I consider myself as an experienced java developer and I will be glad to help you. Best regards Peter Fassev -- 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-digester (in module jakarta-commons) 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-digester has an issue affecting its community integration. This issue affects 49 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - authx-example : Apache Authentication and Authorization Framework - commons-betwixt : Commons Betwixt Package - commons-chain : GoF Chain of Responsibility pattern - commons-configuration : Jakarta commons - commons-digester : XML to Java Object Configuration - commons-digester-rss : Digester RSS Example - commons-jelly-tags-betwixt : Commons Jelly - commons-jelly-tags-jms : Commons Jelly - commons-jelly-tags-quartz : Commons Jelly - commons-messenger : A web based JMS framework - commons-modeler : Modeler MBeans - commons-services : Basic Services Architecture - commons-validator : Validation Framework - db-ddlutils : Easy-to-use component for working with Database Definition (... - eyebrowse : Web-based mail archive browsing - fulcrum-cache : Services Framework - fulcrum-configuration-impl : Services Framework - fulcrum-intake : Services Framework - fulcrum-parser : Services Framework - fulcrum-quartz : Services Framework - fulcrum-security-memory : Services Framework - fulcrum-security-nt : Services Framework - fulcrum-template : Services Framework - invicta : Open-source build management tool. - jakarta-lucene : Java Based Search Engine - jakarta-taglibs-jmstags : JMS Taglib - jakarta-tomcat : Servlet 2.2 and JSP 1.1 Reference Implementation - jakarta-tomcat-4.0 : Servlet 2.3 and JSP 1.2 Reference Implementation - jakarta-tomcat-catalina : Servlet 2.4 Reference Implementation - jakarta-tomcat-coyote : Connectors to various web servers - jakarta-tomcat-coyote-tomcat3 : Connectors to various web servers - jakarta-tomcat-coyote-tomcat4 : Connectors to various web servers - jakarta-tomcat-http11 : Connectors to various web servers - jakarta-tomcat-jk : Connectors to various web servers - jakarta-turbine-jcs : Cache - lucene-java : Java Based Search Engine - maven : Project Management Tools - maven-bootstrap : Project Management Tools - myfaces : JavaServer(tm) Faces implementation - naming-config : Apache Directory Naming Component - portals-bridges-frameworks : Support for JSR168 compliant Portlet development - portals-bridges-jsf : Support for JSR168 compliant Portlet development - portals-bridges-struts : Support for JSR168 compliant Portlet development - portals-bridges-velocity : Support for JSR168 compliant Portlet development - quartz : Job Scheduler - struts-sslext : The Struts SSL Extension for HTTP/HTTPS switching - tapestry : Component-based web application framework organized around i... - tomcat-catalina : Servlet 2.3 and JSP 1.2 Reference Implementation - velocity-tools : VelocityTools project Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons/commons-digester/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-digester.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons/commons-digester/gump_work/build_jakarta-commons_commons-digester.html Work Name: build_jakarta-commons_commons-digester (Type: Build) Work ended in a state of : Failed Elapsed: 5 secs Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true -Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only dist [Working Directory: /srv/gump/public/workspace/jakarta-commons/digester] CLASSPATH:
[EMAIL PROTECTED]: Project commons-digester (in module jakarta-commons) 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-digester has an issue affecting its community integration. This issue affects 49 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - authx-example : Apache Authentication and Authorization Framework - commons-betwixt : Commons Betwixt Package - commons-chain : GoF Chain of Responsibility pattern - commons-configuration : Jakarta commons - commons-digester : XML to Java Object Configuration - commons-digester-rss : Digester RSS Example - commons-jelly-tags-betwixt : Commons Jelly - commons-jelly-tags-jms : Commons Jelly - commons-jelly-tags-quartz : Commons Jelly - commons-messenger : A web based JMS framework - commons-modeler : Modeler MBeans - commons-services : Basic Services Architecture - commons-validator : Validation Framework - db-ddlutils : Easy-to-use component for working with Database Definition (... - eyebrowse : Web-based mail archive browsing - fulcrum-cache : Services Framework - fulcrum-configuration-impl : Services Framework - fulcrum-intake : Services Framework - fulcrum-parser : Services Framework - fulcrum-quartz : Services Framework - fulcrum-security-memory : Services Framework - fulcrum-security-nt : Services Framework - fulcrum-template : Services Framework - invicta : Open-source build management tool. - jakarta-lucene : Java Based Search Engine - jakarta-taglibs-jmstags : JMS Taglib - jakarta-tomcat : Servlet 2.2 and JSP 1.1 Reference Implementation - jakarta-tomcat-4.0 : Servlet 2.3 and JSP 1.2 Reference Implementation - jakarta-tomcat-catalina : Servlet 2.4 Reference Implementation - jakarta-tomcat-coyote : Connectors to various web servers - jakarta-tomcat-coyote-tomcat3 : Connectors to various web servers - jakarta-tomcat-coyote-tomcat4 : Connectors to various web servers - jakarta-tomcat-http11 : Connectors to various web servers - jakarta-tomcat-jk : Connectors to various web servers - jakarta-turbine-jcs : Cache - lucene-java : Java Based Search Engine - maven : Project Management Tools - maven-bootstrap : Project Management Tools - myfaces : JavaServer(tm) Faces implementation - naming-config : Apache Directory Naming Component - portals-bridges-frameworks : Support for JSR168 compliant Portlet development - portals-bridges-jsf : Support for JSR168 compliant Portlet development - portals-bridges-struts : Support for JSR168 compliant Portlet development - portals-bridges-velocity : Support for JSR168 compliant Portlet development - quartz : Job Scheduler - struts-sslext : The Struts SSL Extension for HTTP/HTTPS switching - tapestry : Component-based web application framework organized around i... - tomcat-catalina : Servlet 2.3 and JSP 1.2 Reference Implementation - velocity-tools : VelocityTools project Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons/commons-digester/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-digester.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons/commons-digester/gump_work/build_jakarta-commons_commons-digester.html Work Name: build_jakarta-commons_commons-digester (Type: Build) Work ended in a state of : Failed Elapsed: 5 secs Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true -Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only dist [Working Directory: /srv/gump/public/workspace/jakarta-commons/digester] CLASSPATH:
[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-19072007.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-19072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-19072007.jar:/srv/gump/public/workspace/junit/dist/junit-19072007.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: Thu Jul 19 01:09:53 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 0519072007, vmgump:vmgump-public:0519072007 Gump E-mail Identifier (unique within run) #30. -- 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-19072007.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-19072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-19072007.jar:/srv/gump/public/workspace/junit/dist/junit-19072007.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: Thu Jul 19 01:09:53 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 0519072007, vmgump:vmgump-public:0519072007 Gump E-mail Identifier (unique within run) #30. -- 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
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: 13 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-19072007.jar:/srv/gump/public/workspace/jakarta-commons/collections/build/commons-collections-19072007.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-19072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-19072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-19072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-19072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-19072007.jar:/srv/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-19072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-19072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-19072007.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-19072007.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
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: 13 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-19072007.jar:/srv/gump/public/workspace/jakarta-commons/collections/build/commons-collections-19072007.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-19072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-19072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-19072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-19072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-19072007.jar:/srv/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-19072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-19072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-19072007.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-19072007.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
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-19072007.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-19072007.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-19072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-19072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-19072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xmlunit/target/commons-jelly-tags-xmlunit-19072007.jar:/srv/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-19072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-19072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-19072007.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-19072007.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-19072007.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
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-19072007.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-19072007.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-19072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-19072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-19072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xmlunit/target/commons-jelly-tags-xmlunit-19072007.jar:/srv/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-19072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-19072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-19072007.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-19072007.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-19072007.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] Commented: (TRANSACTION-9) [transaction] Add full file management capabilities to the FileResourceManager
[ https://issues.apache.org/jira/browse/TRANSACTION-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513906 ] Jörg Heinicke commented on TRANSACTION-9: - There seems to be an inconsistency: How to lock a not-yet-existing physical resource that is about to be created? We can follow the java.io.File semantics here and allow Resource instantiation for non-existing physical resources. Then Resource should have a create method as File has. Otherwise lock methods should be moved to ResourceManager. I prefer the first one which removes create* from ResourceManager. I wonder if we need the generalization Property. Also, in which way is the key in the map different from the name of the Property? If we do it the generalized way I'd use getProperty(String) and setProperty(String, Object), maybe additionally a getPropertyNames(). The Map is implementation. And always being forced to set all properties at once using setProperties(Map) does not make much sense IMO. readStream() and writeStream() should be in Java Bean style with get. What's the use of try*Lock()? [transaction] Add full file management capabilities to the FileResourceManager -- Key: TRANSACTION-9 URL: https://issues.apache.org/jira/browse/TRANSACTION-9 Project: Commons Transaction Issue Type: Improvement Environment: Operating System: All Platform: All Reporter: Peter Fassev Assignee: Oliver Zeigermann Priority: Minor Fix For: 2.0 Attachments: filemanager.zip Hi, As stated in the doc the FileResourceManager is: A resource manager for streamable objects stored in a file system I agree, that this is a resource manager, but it could be easily extended, to support a full file management system. It will be very helpful to have additional methods like renameResource(), getResourceSize(), getResourceTime(), setResourceTime() etc. This are common file operations, which should be managed by the FileResourceManager. Further it will be very helpful to have (real) support for resource collections (folders). It will be necessary to distinguish between single resources (files) and collections (folders). Together, this features will enable a transactional access to any file based resources - for instance a document repository. Are there plans for such extensions and if not, will they actually fit in the goals of the transaction library? If not, please open the underlying structure, like the inner class TransactionContext, in order to add extensions the file management. For instance, it will be good to have a separate factory method, which creates the context. If you are interested in this proposal, I am ready to contribute to this project. I consider myself as an experienced java developer and I will be glad to help you. Best regards Peter Fassev -- 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
Yes, you do, use the filecommonupload old version... i'm usin that version, i dont remember what number because i'm not stay in my office. If you can, writeme to [EMAIL PROTECTED] to remember and send the code for the group and for you. atte. Walter E. Zegarra Synopsis Developer [EMAIL PROTECTED] Lima - Peru 2007/7/18, Martin Cooper [EMAIL PROTECTED]: 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 -- Don´t Worry Be Walter Alexita!!!
[jira] Commented: (TRANSACTION-9) [transaction] Add full file management capabilities to the FileResourceManager
[ https://issues.apache.org/jira/browse/TRANSACTION-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513925 ] Oliver Zeigermann commented on TRANSACTION-9: - I do agree concerning properties and Resource vs. ResourceManager. This is my new proposal public interface Resource { String getPath(); boolean isDirectory(); boolean isFile(); CollectionResource getChildren() throws IOException, LockException; Resource getParent() throws IOException, LockException; InputStream readStream() throws IOException, LockException; OutputStream writeStream() throws IOException, LockException; boolean delete() throws IOException, LockException; boolean move(String destinationpath) throws IOException, LockException; boolean copy(String destinationpath) throws IOException, LockException; boolean exists(); void createDirectory() throws IOException, LockException; void createFile() throws IOException, LockException; // plus more general properties // among them could be length, lastmodfied, etc. Object getProperty(String name); Object setProperty(String name, Object newValue); // plus locking methods void readLock(); void writeLock(); boolean tryReadLock(); boolean tryWriteLock(); } public interface FileResourceManager { Resource getResource(String path) throws IOException, LockException; void addResourceListener(ResourceListener listener); void removeResourceListener(ResourceListener listener); } However, I do not agree to use bean style here, as this is no bean. This is an interface. It should not have bean style getters/setters. Concerning try*Lock(): These methods are fail fast version of the lock*() ones which can be used to check whether you *could* acqurie a lock or not. They make sense if you just want to know. [transaction] Add full file management capabilities to the FileResourceManager -- Key: TRANSACTION-9 URL: https://issues.apache.org/jira/browse/TRANSACTION-9 Project: Commons Transaction Issue Type: Improvement Environment: Operating System: All Platform: All Reporter: Peter Fassev Assignee: Oliver Zeigermann Priority: Minor Fix For: 2.0 Attachments: filemanager.zip Hi, As stated in the doc the FileResourceManager is: A resource manager for streamable objects stored in a file system I agree, that this is a resource manager, but it could be easily extended, to support a full file management system. It will be very helpful to have additional methods like renameResource(), getResourceSize(), getResourceTime(), setResourceTime() etc. This are common file operations, which should be managed by the FileResourceManager. Further it will be very helpful to have (real) support for resource collections (folders). It will be necessary to distinguish between single resources (files) and collections (folders). Together, this features will enable a transactional access to any file based resources - for instance a document repository. Are there plans for such extensions and if not, will they actually fit in the goals of the transaction library? If not, please open the underlying structure, like the inner class TransactionContext, in order to add extensions the file management. For instance, it will be good to have a separate factory method, which creates the context. If you are interested in this proposal, I am ready to contribute to this project. I consider myself as an experienced java developer and I will be glad to help you. Best regards Peter Fassev -- 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: [BeanUtils] Progressing towards a 1.8.0 release
On 7/19/07, Stephen Colebourne [EMAIL PROTECTED] wrote: Henri Yandell wrote: On 7/17/07, Niall Pemberton [EMAIL PROTECTED] wrote: Assemblies work except you only get a default manifest - not sure where I got the attachment idea from, can't find any reference to that - so I think we should keep it simple and stick to option #1 That has my +1 [obviously]. I think we should keep it simple. But surely, the problem is that maven will pull in collections.jar when it pulls in beanutils.jar, which is unnecessary. Its big, unnecessary dependencies like this that give commons a bad name. Using maven2 we can specify the dependency as optional - which means Collections won't get pulled in unless the depenency is specifically defined in a users project: http://tinyurl.com/2nm2bu Again, just to repeat in case the point was missed - that optional dependency already exists in commons-beanutils.jar for 1.7.0 - it just wasn't declared in the pom (1.7.0 was built using ant). Bizarely there is a pom (on ibiblio) for commons-beanutils-core.jar (which doesn't have any Collections dependency) and that DOES have a Collections dependency declared. So for BeanUtils 1.7.0 you get Collections when you don't need it and you don't get it when you do need it!!! Niall Anyway, I'll not block this, if this is the way you want to go. Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (BEANUTILS-290) Merge Bean-Collections back into core BeanUtils and remove Bean-Collections sub-project
Merge Bean-Collections back into core BeanUtils and remove Bean-Collections sub-project --- Key: BEANUTILS-290 URL: https://issues.apache.org/jira/browse/BEANUTILS-290 Project: Commons BeanUtils Issue Type: Task Components: Bean-Collections Affects Versions: 1.7.0 Reporter: Niall Pemberton Assignee: Niall Pemberton Priority: Minor Fix For: 1.8.0 This issue has been discussed in the following thread: http://tinyurl.com/2xdpku For BeanUtils 1.7.0 the following classes which had a dependency on Commons Collections were split into a separate bean-collections sub-module: BeanComparator.java BeanMap.java BeanPredicate.java BeanPropertyValueChangeClosure.java BeanPropertyValueEqualsPredicate.java BeanToPropertyValueTransformer.java Three flavours of jars were released in 1.7.0 commons-beanutils.jar - containing all BeanUtils classes, including above bean-collections ones commons-beanutils-bean-collections.jar - containing just the above bean-collections classes commons-beanutils-core.jar - containing BeanUtils classes excluding above bean-collections ones BeanUtils 1.7.0 was created using ant and (I presume) the maven poms for the above artifacts were manually created - unfortunately with mistakes: 1) The pom for commons-beanutils.jar DOESN'T declare any Commons Collections dependency (which it has for the bean-collections classes) 2) The pom for commons-beanutils-core.jar DOES declare a Commons Collections dependency (which it doesn't actually have) The proposal for BeanUtils 1.8.0 (see http://tinyurl.com/2xdpku) is to merge the bean-collections classes back into core BeanUtils and get rid of the bean-collections sub-module - releasing just a single jar for BeanUtils and marking the Commons Collections dependency as optional in the maven pom (see http://tinyurl.com/2nm2bu). -- 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: [BeanUtils] Progressing towards a 1.8.0 release
On 7/18/07, Henri Yandell [EMAIL PROTECTED] wrote: On 7/17/07, Niall Pemberton [EMAIL PROTECTED] wrote: On 7/17/07, Niall Pemberton [EMAIL PROTECTED] wrote: On 7/17/07, Henri Yandell [EMAIL PROTECTED] wrote: My view is that we have the following options: 1) Merge em back in and just release the 1 jar. 2) Split them; do not release a beanutils.jar (or if we do, it's beanutils-core renamed) and setup beanutils-collections as a separate component in Commons or as a child of beanutils with core as an equivalent child (ie: Maven2 multiproject). I don't want to do a maven multi-project - but I also don't see whats wrong with releasing the three jars as they were last time - as I said eariler in this thread - merge in the bean-collections sub-project, but use an assembly to re-create the core and bean-collections jars. As attached artifacts then people would have the option to depend on those if they so desired (as my understanding of maven goes). Assemblies work except you only get a default manifest - not sure where I got the attachment idea from, can't find any reference to that - so I think we should keep it simple and stick to option #1 That has my +1 [obviously]. I think we should keep it simple. As the majority are in favour and with no-one vetoing this proposal - I'll go ahead and do this later tonight. I created a Jira issue[1] to document this (since they're far easier to find later down the road than mailing list threads) [1] https://issues.apache.org/jira/browse/BEANUTILS-290 Niall Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [logging] Running tests on earlier JVMs
Anyone? Dennis Lundberg wrote: Hi I'm trying to put together an an script that will do nothing more than run the tests for commons logging. It's going fairly well. A couple of issues that I found though that I need assistance with. Failing test The two test files in the security package both fail. These tests were run using a 1.3 jvm (see below why that is). Testsuite: org.apache.commons.logging.security.SecurityAllowedTestCase Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0,016 sec - Standard Output --- testing permission:class java.util.PropertyPermission:(java.util.PropertyPermission sun.net.inetaddr.ttl read) - --- Testcase: testAllAllowed took 0,016 sec Caused an ERROR null java.lang.NoClassDefFoundError at java.lang.System.setSecurityManager0(System.java:239) at java.lang.System.setSecurityManager(System.java:208) at org.apache.commons.logging.security.SecurityAllowedTestCase.tearDown(SecurityAllowedTestCase.java:77) at org.apache.commons.logging.PathableTestSuite.runTest(PathableTestSuite.java:142) Testsuite: org.apache.commons.logging.security.SecurityForbiddenTestCase Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0,015 sec Testcase: testAllForbidden took 0,015 sec Caused an ERROR null java.lang.NoClassDefFoundError at java.lang.System.setSecurityManager0(System.java:239) at java.lang.System.setSecurityManager(System.java:208) at org.apache.commons.logging.security.SecurityForbiddenTestCase.tearDown(SecurityForbiddenTestCase.java:80) at org.apache.commons.logging.PathableTestSuite.runTest(PathableTestSuite.java:142) Finding a (really old) platform to run on = We've said earlier that we should ideally run the tests using a 1.2 jvm. So I installed 1.2.2_17 on my Windows machine and started running tests. That didn't go to well. Here's what I get: Buildfile: build-testing.xml A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/Project.addReference (Ljava/lang/String;Ljava/lang/Object;)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/Project.fireMessageLoggedEvent (Lorg/apache/tools/ant/BuildEvent;Ljava/lang/String;I)V': Interpreting method . Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/ComponentHelper.addCreatedTask (Ljava/lang/String;Lorg/apache/tools/ant/Task;)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi init: [echo] Logging Wrapper Library 1.1.1-SNAPSHOT discovery: log4j12-test-warning: test: [echo] Test output can be found in directory G:\apache\jakarta\commons-logging/target/test-reports. [delete] Deleting directory G:\apache\jakarta\commons-logging\target\test-reports [mkdir] Created dir: G:\apache\jakarta\commons-logging\target\test-reports [echo] executing tests [**/*TestCase.java] A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/ComponentHelper.getDataTypeDefinitions ()Ljava/util/Hashtable;': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/DirectoryScanner.scan ()V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/util/FileUtils.createTempFile (Ljava/lang/String;Ljava/lang/String;Ljava/io/File;)Ljava/io/File;': Interpret ing method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/taskdefs/ProcessDestroyer.add (Ljava/lang/Process;)Z': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi [junit] java.lang.IllegalMonitorStateException: current thread not owner [junit] at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.java, Compiled Code) [junit] at java.lang.Thread.run(Thread.java:479) [junit] java.lang.IllegalMonitorStateException: current thread not owner [junit] at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.java, Compiled Code) [junit] at java.lang.Thread.run(Thread.java:479) And then it just hangs! This is done using ant
[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_12513979 ] Rahul Akolkar commented on DIGESTER-115: But a tighter ArrayStack wouldn't work (given fix version is 1.8.1). In the longer run, I agree, we should wean [digester] off of the [collections] version of ArrayStack (doing what you suggest or just using java.util.Stack or some such so we will have one less class to maintain). 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]
Commons Logging 1.1.1 - when?
Are there plans to release Commons Logging 1.1.1? I am eager to see Commons Logging 1.1.1 because JCL 1.1 throws exceptions when running in a Java applet sandbox. (This bug is already fixed: https://issues.apache.org/jira/browse/LOGGING-106) The roadmap shows 4 issues that are resolved in Commons Logging 1.1.1: https://issues.apache.org/jira/browse/LOGGING?report=com.atlassian.jira. plugin.system.project:roadmap-panel Is anybody working on JCL 1.1.1? Thanks, Sean
Re: Commons Logging 1.1.1 - when?
On 7/19/07, Sullivan, Sean [EMAIL PROTECTED] wrote: Are there plans to release Commons Logging 1.1.1? I am eager to see Commons Logging 1.1.1 because JCL 1.1 throws exceptions when running in a Java applet sandbox. (This bug is already fixed: https://issues.apache.org/jira/browse/LOGGING-106) The roadmap shows 4 issues that are resolved in Commons Logging 1.1.1: Plus I seem to recall that when I was digging through it for work, I found a significant bugfix that wasn't in JIRA. https://issues.apache.org/jira/browse/LOGGING?report=com.atlassian.jira. plugin.system.project:roadmap-panel Is anybody working on JCL 1.1.1? Not afaik. I put some effort in a bit back, but the release process was too confusing for the time I wanted to put in. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [logging] Running tests on earlier JVMs
So sounds like we need an older version of Ant. Do the Security errors happen on more modern JVMs? Are they new tests? On 7/19/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Anyone? Dennis Lundberg wrote: Hi I'm trying to put together an an script that will do nothing more than run the tests for commons logging. It's going fairly well. A couple of issues that I found though that I need assistance with. Failing test The two test files in the security package both fail. These tests were run using a 1.3 jvm (see below why that is). Testsuite: org.apache.commons.logging.security.SecurityAllowedTestCase Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0,016 sec - Standard Output --- testing permission:class java.util.PropertyPermission:(java.util.PropertyPermission sun.net.inetaddr.ttl read) - --- Testcase: testAllAllowed took 0,016 sec Caused an ERROR null java.lang.NoClassDefFoundError at java.lang.System.setSecurityManager0(System.java:239) at java.lang.System.setSecurityManager(System.java:208) at org.apache.commons.logging.security.SecurityAllowedTestCase.tearDown(SecurityAllowedTestCase.java:77) at org.apache.commons.logging.PathableTestSuite.runTest(PathableTestSuite.java:142) Testsuite: org.apache.commons.logging.security.SecurityForbiddenTestCase Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0,015 sec Testcase: testAllForbidden took 0,015 sec Caused an ERROR null java.lang.NoClassDefFoundError at java.lang.System.setSecurityManager0(System.java:239) at java.lang.System.setSecurityManager(System.java:208) at org.apache.commons.logging.security.SecurityForbiddenTestCase.tearDown(SecurityForbiddenTestCase.java:80) at org.apache.commons.logging.PathableTestSuite.runTest(PathableTestSuite.java:142) Finding a (really old) platform to run on = We've said earlier that we should ideally run the tests using a 1.2 jvm. So I installed 1.2.2_17 on my Windows machine and started running tests. That didn't go to well. Here's what I get: Buildfile: build-testing.xml A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/Project.addReference (Ljava/lang/String;Ljava/lang/Object;)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/Project.fireMessageLoggedEvent (Lorg/apache/tools/ant/BuildEvent;Ljava/lang/String;I)V': Interpreting method . Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/ComponentHelper.addCreatedTask (Ljava/lang/String;Lorg/apache/tools/ant/Task;)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi init: [echo] Logging Wrapper Library 1.1.1-SNAPSHOT discovery: log4j12-test-warning: test: [echo] Test output can be found in directory G:\apache\jakarta\commons-logging/target/test-reports. [delete] Deleting directory G:\apache\jakarta\commons-logging\target\test-reports [mkdir] Created dir: G:\apache\jakarta\commons-logging\target\test-reports [echo] executing tests [**/*TestCase.java] A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/ComponentHelper.getDataTypeDefinitions ()Ljava/util/Hashtable;': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/DirectoryScanner.scan ()V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/util/FileUtils.createTempFile (Ljava/lang/String;Ljava/lang/String;Ljava/io/File;)Ljava/io/File;': Interpret ing method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/taskdefs/ProcessDestroyer.add (Ljava/lang/Process;)Z': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi [junit] java.lang.IllegalMonitorStateException: current thread not owner [junit] at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.java, Compiled Code) [junit] at java.lang.Thread.run(Thread.java:479) [junit] java.lang.IllegalMonitorStateException: current
Re: Commons Logging 1.1.1 - when?
On 7/19/07, Henri Yandell [EMAIL PROTECTED] wrote: On 7/19/07, Sullivan, Sean [EMAIL PROTECTED] wrote: Are there plans to release Commons Logging 1.1.1? I am eager to see Commons Logging 1.1.1 because JCL 1.1 throws exceptions when running in a Java applet sandbox. (This bug is already fixed: https://issues.apache.org/jira/browse/LOGGING-106) The roadmap shows 4 issues that are resolved in Commons Logging 1.1.1: Plus I seem to recall that when I was digging through it for work, I found a significant bugfix that wasn't in JIRA. https://issues.apache.org/jira/browse/LOGGING?report=com.atlassian.jira. plugin.system.project:roadmap-panel Is anybody working on JCL 1.1.1? Not afaik. I put some effort in a bit back, but the release process was too confusing for the time I wanted to put in. Is it worth pinging Simon or Robert (last 2 release managers) directly for help - this may be going under their radar. Niall Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Commons Logging 1.1.1 - when?
On 7/19/07, Niall Pemberton [EMAIL PROTECTED] wrote: On 7/19/07, Henri Yandell [EMAIL PROTECTED] wrote: On 7/19/07, Sullivan, Sean [EMAIL PROTECTED] wrote: Are there plans to release Commons Logging 1.1.1? I am eager to see Commons Logging 1.1.1 because JCL 1.1 throws exceptions when running in a Java applet sandbox. (This bug is already fixed: https://issues.apache.org/jira/browse/LOGGING-106) The roadmap shows 4 issues that are resolved in Commons Logging 1.1.1: Plus I seem to recall that when I was digging through it for work, I found a significant bugfix that wasn't in JIRA. https://issues.apache.org/jira/browse/LOGGING?report=com.atlassian.jira. plugin.system.project:roadmap-panel Is anybody working on JCL 1.1.1? Not afaik. I put some effort in a bit back, but the release process was too confusing for the time I wanted to put in. Is it worth pinging Simon or Robert (last 2 release managers) directly for help - this may be going under their radar. Doh! wrong thread :( Niall Niall Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [logging] Running tests on earlier JVMs
Is it worth pinging Simon or Robert (last 2 release managers) directly for help - this may be going under their radar. Niall On 7/19/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Anyone? Dennis Lundberg wrote: Hi I'm trying to put together an an script that will do nothing more than run the tests for commons logging. It's going fairly well. A couple of issues that I found though that I need assistance with. Failing test The two test files in the security package both fail. These tests were run using a 1.3 jvm (see below why that is). Testsuite: org.apache.commons.logging.security.SecurityAllowedTestCase Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0,016 sec - Standard Output --- testing permission:class java.util.PropertyPermission:(java.util.PropertyPermission sun.net.inetaddr.ttl read) - --- Testcase: testAllAllowed took 0,016 sec Caused an ERROR null java.lang.NoClassDefFoundError at java.lang.System.setSecurityManager0(System.java:239) at java.lang.System.setSecurityManager(System.java:208) at org.apache.commons.logging.security.SecurityAllowedTestCase.tearDown(SecurityAllowedTestCase.java:77) at org.apache.commons.logging.PathableTestSuite.runTest(PathableTestSuite.java:142) Testsuite: org.apache.commons.logging.security.SecurityForbiddenTestCase Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0,015 sec Testcase: testAllForbidden took 0,015 sec Caused an ERROR null java.lang.NoClassDefFoundError at java.lang.System.setSecurityManager0(System.java:239) at java.lang.System.setSecurityManager(System.java:208) at org.apache.commons.logging.security.SecurityForbiddenTestCase.tearDown(SecurityForbiddenTestCase.java:80) at org.apache.commons.logging.PathableTestSuite.runTest(PathableTestSuite.java:142) Finding a (really old) platform to run on = We've said earlier that we should ideally run the tests using a 1.2 jvm. So I installed 1.2.2_17 on my Windows machine and started running tests. That didn't go to well. Here's what I get: Buildfile: build-testing.xml A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/Project.addReference (Ljava/lang/String;Ljava/lang/Object;)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/Project.fireMessageLoggedEvent (Lorg/apache/tools/ant/BuildEvent;Ljava/lang/String;I)V': Interpreting method . Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/ComponentHelper.addCreatedTask (Ljava/lang/String;Lorg/apache/tools/ant/Task;)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi init: [echo] Logging Wrapper Library 1.1.1-SNAPSHOT discovery: log4j12-test-warning: test: [echo] Test output can be found in directory G:\apache\jakarta\commons-logging/target/test-reports. [delete] Deleting directory G:\apache\jakarta\commons-logging\target\test-reports [mkdir] Created dir: G:\apache\jakarta\commons-logging\target\test-reports [echo] executing tests [**/*TestCase.java] A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/ComponentHelper.getDataTypeDefinitions ()Ljava/util/Hashtable;': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/DirectoryScanner.scan ()V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/util/FileUtils.createTempFile (Ljava/lang/String;Ljava/lang/String;Ljava/io/File;)Ljava/io/File;': Interpret ing method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/taskdefs/ProcessDestroyer.add (Ljava/lang/Process;)Z': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi [junit] java.lang.IllegalMonitorStateException: current thread not owner [junit] at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.java, Compiled Code) [junit] at java.lang.Thread.run(Thread.java:479) [junit] java.lang.IllegalMonitorStateException:
[csv] getting involved
Announcing my intent to commit in [csv]. I'll be starting small... -Matt Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=listsid=396545433 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TRANSACTION-9) [transaction] Add full file management capabilities to the FileResourceManager
[ https://issues.apache.org/jira/browse/TRANSACTION-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513982 ] Peter Fassev commented on TRANSACTION-9: Yes, tryLock make sense when locking a set of arbitrary resources prior to any operation on it, and as Oliver said, it reduces the chance of a deadlock. And I think it is possible to lock a not existing resource, because the locking does not depend from the underlying file system. It all about Ids, and a not created resource has an Id. Again, if you want to create a set of resource at once, you may try to lock them first, and than execute the creation method independently. Sorry, for my insistence here, but I am talking about a resource management systems in a multi user environment. Such scenarios are very common there. For instance, think about of uploading a directory structure as a large ZIP-Archive and than extracting all of it files. Or what about downloading a whole directory structure as a ZIP-Archive... One thought about directories: Adding a file to, renaming a file or deleting a file from, or even changing a file in a directory actually changes the structure of the directory. Before committing such changes, read lock on the directory is not sufficient for this operation. The directory should have a write lock, because somebody may try to read the children during the committing operation (i.e. during the changes) and may become a inconsistent state of it. So my attached implementation here is not quite gut on this point. [transaction] Add full file management capabilities to the FileResourceManager -- Key: TRANSACTION-9 URL: https://issues.apache.org/jira/browse/TRANSACTION-9 Project: Commons Transaction Issue Type: Improvement Environment: Operating System: All Platform: All Reporter: Peter Fassev Assignee: Oliver Zeigermann Priority: Minor Fix For: 2.0 Attachments: filemanager.zip Hi, As stated in the doc the FileResourceManager is: A resource manager for streamable objects stored in a file system I agree, that this is a resource manager, but it could be easily extended, to support a full file management system. It will be very helpful to have additional methods like renameResource(), getResourceSize(), getResourceTime(), setResourceTime() etc. This are common file operations, which should be managed by the FileResourceManager. Further it will be very helpful to have (real) support for resource collections (folders). It will be necessary to distinguish between single resources (files) and collections (folders). Together, this features will enable a transactional access to any file based resources - for instance a document repository. Are there plans for such extensions and if not, will they actually fit in the goals of the transaction library? If not, please open the underlying structure, like the inner class TransactionContext, in order to add extensions the file management. For instance, it will be good to have a separate factory method, which creates the context. If you are interested in this proposal, I am ready to contribute to this project. I consider myself as an experienced java developer and I will be glad to help you. Best regards Peter Fassev -- 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: jakarta/apache email subscription
I'm tired of getting all these emails and cannot get unsubscribed from this list!!! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
re: jakarta/apache email subscription
I'm tired of getting all these emails and cannot get unsubscribed from this list!!! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [logging] Running tests on earlier JVMs
Henri Yandell wrote: So sounds like we need an older version of Ant. Like I said (way below) I tried using ant 1.5.4, but that didn't work because the build script is using features that were added to ant 1.6. Do the Security errors happen on more modern JVMs? Are they new tests? They work fine on 1.4.2 for me. They were added, by Simon, to test one of the bugs that were fixed in 1.1.1. On 7/19/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Anyone? Dennis Lundberg wrote: Hi I'm trying to put together an an script that will do nothing more than run the tests for commons logging. It's going fairly well. A couple of issues that I found though that I need assistance with. Failing test The two test files in the security package both fail. These tests were run using a 1.3 jvm (see below why that is). Testsuite: org.apache.commons.logging.security.SecurityAllowedTestCase Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0,016 sec - Standard Output --- testing permission:class java.util.PropertyPermission:(java.util.PropertyPermission sun.net.inetaddr.ttl read) - --- Testcase: testAllAllowed took 0,016 sec Caused an ERROR null java.lang.NoClassDefFoundError at java.lang.System.setSecurityManager0(System.java:239) at java.lang.System.setSecurityManager(System.java:208) at org.apache.commons.logging.security.SecurityAllowedTestCase.tearDown(SecurityAllowedTestCase.java:77) at org.apache.commons.logging.PathableTestSuite.runTest(PathableTestSuite.java:142) Testsuite: org.apache.commons.logging.security.SecurityForbiddenTestCase Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0,015 sec Testcase: testAllForbidden took 0,015 sec Caused an ERROR null java.lang.NoClassDefFoundError at java.lang.System.setSecurityManager0(System.java:239) at java.lang.System.setSecurityManager(System.java:208) at org.apache.commons.logging.security.SecurityForbiddenTestCase.tearDown(SecurityForbiddenTestCase.java:80) at org.apache.commons.logging.PathableTestSuite.runTest(PathableTestSuite.java:142) Finding a (really old) platform to run on = We've said earlier that we should ideally run the tests using a 1.2 jvm. So I installed 1.2.2_17 on my Windows machine and started running tests. That didn't go to well. Here's what I get: Buildfile: build-testing.xml A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/Project.addReference (Ljava/lang/String;Ljava/lang/Object;)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/Project.fireMessageLoggedEvent (Lorg/apache/tools/ant/BuildEvent;Ljava/lang/String;I)V': Interpreting method . Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/ComponentHelper.addCreatedTask (Ljava/lang/String;Lorg/apache/tools/ant/Task;)V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi init: [echo] Logging Wrapper Library 1.1.1-SNAPSHOT discovery: log4j12-test-warning: test: [echo] Test output can be found in directory G:\apache\jakarta\commons-logging/target/test-reports. [delete] Deleting directory G:\apache\jakarta\commons-logging\target\test-reports [mkdir] Created dir: G:\apache\jakarta\commons-logging\target\test-reports [echo] executing tests [**/*TestCase.java] A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/ComponentHelper.getDataTypeDefinitions ()Ljava/util/Hashtable;': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/DirectoryScanner.scan ()V': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/util/FileUtils.createTempFile (Ljava/lang/String;Ljava/lang/String;Ljava/io/File;)Ljava/io/File;': Interpret ing method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi A nonfatal internal JIT (3.10.107(x)) error 'chgTarg: Conditional' has occurred in : 'org/apache/tools/ant/taskdefs/ProcessDestroyer.add (Ljava/lang/Process;)Z': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi
svn commit: r557796 - in /jakarta/commons/proper/beanutils/trunk: ./ optional/ src/java/org/apache/commons/beanutils/ src/site/ src/test/org/apache/commons/beanutils/ xdocs/
Author: niallp Date: Thu Jul 19 15:28:49 2007 New Revision: 557796 URL: http://svn.apache.org/viewvc?view=revrev=557796 Log: BEANUTILS-290 - Merge Bean-Collections back into core BeanUtils and remove Bean-Collections sub-project Added: jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/BeanComparator.java - copied unchanged from r557757, jakarta/commons/proper/beanutils/trunk/optional/bean-collections/src/java/org/apache/commons/beanutils/BeanComparator.java jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/BeanMap.java - copied unchanged from r557757, jakarta/commons/proper/beanutils/trunk/optional/bean-collections/src/java/org/apache/commons/beanutils/BeanMap.java jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/BeanPredicate.java - copied unchanged from r557757, jakarta/commons/proper/beanutils/trunk/optional/bean-collections/src/java/org/apache/commons/beanutils/BeanPredicate.java jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/BeanPropertyValueChangeClosure.java - copied unchanged from r557757, jakarta/commons/proper/beanutils/trunk/optional/bean-collections/src/java/org/apache/commons/beanutils/BeanPropertyValueChangeClosure.java jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/BeanPropertyValueEqualsPredicate.java - copied unchanged from r557757, jakarta/commons/proper/beanutils/trunk/optional/bean-collections/src/java/org/apache/commons/beanutils/BeanPropertyValueEqualsPredicate.java jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/BeanToPropertyValueTransformer.java - copied unchanged from r557757, jakarta/commons/proper/beanutils/trunk/optional/bean-collections/src/java/org/apache/commons/beanutils/BeanToPropertyValueTransformer.java jakarta/commons/proper/beanutils/trunk/src/test/org/apache/commons/beanutils/BeanComparatorTestCase.java - copied unchanged from r557757, jakarta/commons/proper/beanutils/trunk/optional/bean-collections/src/test/org/apache/commons/beanutils/BeanComparatorTestCase.java jakarta/commons/proper/beanutils/trunk/src/test/org/apache/commons/beanutils/BeanMapTestCase.java - copied, changed from r557757, jakarta/commons/proper/beanutils/trunk/optional/bean-collections/src/test/org/apache/commons/beanutils/TestBeanMap.java jakarta/commons/proper/beanutils/trunk/src/test/org/apache/commons/beanutils/BeanPredicateTestCase.java - copied unchanged from r557757, jakarta/commons/proper/beanutils/trunk/optional/bean-collections/src/test/org/apache/commons/beanutils/BeanPredicateTestCase.java jakarta/commons/proper/beanutils/trunk/src/test/org/apache/commons/beanutils/BeanPropertyValueChangeClosureTestCase.java - copied, changed from r557757, jakarta/commons/proper/beanutils/trunk/optional/bean-collections/src/test/org/apache/commons/beanutils/BeanPropertyValueChangeClosureTest.java jakarta/commons/proper/beanutils/trunk/src/test/org/apache/commons/beanutils/BeanPropertyValueEqualsPredicateTestCase.java - copied, changed from r557757, jakarta/commons/proper/beanutils/trunk/optional/bean-collections/src/test/org/apache/commons/beanutils/BeanPropertyValueEqualsPredicateTest.java jakarta/commons/proper/beanutils/trunk/src/test/org/apache/commons/beanutils/BeanToPropertyValueTransformerTestCase.java - copied, changed from r557757, jakarta/commons/proper/beanutils/trunk/optional/bean-collections/src/test/org/apache/commons/beanutils/BeanToPropertyValueTransformerTest.java jakarta/commons/proper/beanutils/trunk/xdocs/bean-collections.xml - copied unchanged from r557757, jakarta/commons/proper/beanutils/trunk/optional/bean-collections/xdocs/index.xml Removed: jakarta/commons/proper/beanutils/trunk/optional/ Modified: jakarta/commons/proper/beanutils/trunk/build.properties.sample jakarta/commons/proper/beanutils/trunk/build.xml jakarta/commons/proper/beanutils/trunk/pom.xml jakarta/commons/proper/beanutils/trunk/project.xml jakarta/commons/proper/beanutils/trunk/src/site/site.xml jakarta/commons/proper/beanutils/trunk/xdocs/navigation.xml Modified: jakarta/commons/proper/beanutils/trunk/build.properties.sample URL: http://svn.apache.org/viewvc/jakarta/commons/proper/beanutils/trunk/build.properties.sample?view=diffrev=557796r1=557795r2=557796 == --- jakarta/commons/proper/beanutils/trunk/build.properties.sample (original) +++ jakarta/commons/proper/beanutils/trunk/build.properties.sample Thu Jul 19 15:28:49 2007 @@ -19,6 +19,7 @@ # The pathname of the collections classes JAR file commons-collections.home=${repository}/commons-collections/jars commons-collections.jar=${commons-collections.home}/commons-collections-3.2.jar
svn commit: r557802 - in /jakarta/commons/proper/beanutils/trunk: maven.xml src/main/assembly/src.xml
Author: niallp Date: Thu Jul 19 15:46:31 2007 New Revision: 557802 URL: http://svn.apache.org/viewvc?view=revrev=557802 Log: BEANUTILS-290 - Missed a couple of changes merging Bean-Collections back into core BeanUtils Modified: jakarta/commons/proper/beanutils/trunk/maven.xml jakarta/commons/proper/beanutils/trunk/src/main/assembly/src.xml Modified: jakarta/commons/proper/beanutils/trunk/maven.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/beanutils/trunk/maven.xml?view=diffrev=557802r1=557801r2=557802 == --- jakarta/commons/proper/beanutils/trunk/maven.xml (original) +++ jakarta/commons/proper/beanutils/trunk/maven.xml Thu Jul 19 15:46:31 2007 @@ -57,11 +57,6 @@ fileset dir=xdocs/ /copy - !-- Copy optional files -- - copy todir=${maven.dist.src.assembly.dir}/optional - fileset dir=optional/ - /copy - /postGoal !-- == -- Modified: jakarta/commons/proper/beanutils/trunk/src/main/assembly/src.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/beanutils/trunk/src/main/assembly/src.xml?view=diffrev=557802r1=557801r2=557802 == --- jakarta/commons/proper/beanutils/trunk/src/main/assembly/src.xml (original) +++ jakarta/commons/proper/beanutils/trunk/src/main/assembly/src.xml Thu Jul 19 15:46:31 2007 @@ -41,14 +41,6 @@ /includes /fileSet fileSet -directoryoptional/directory -excludes -excludebuild.properties/exclude -excludetarget/exclude -excludedist/exclude -/excludes -/fileSet -fileSet directorysrc/directory /fileSet fileSet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (DBCP-209) Is DataSource.getConnection(user, pass) working the way it is suppose to?
[ https://issues.apache.org/jira/browse/DBCP-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514033 ] Dain Sundstrom commented on DBCP-209: - I believe that Michael should be using either the SharedPoolDataSource or the PerUserPoolDataSource which support the getConnection(user, pass) method. This pool keeps track of connection credentials, so when a connection is created, it can locate a connection authorized for the specified user. I think this issue should be closed as invalid. Is DataSource.getConnection(user, pass) working the way it is suppose to? - Key: DBCP-209 URL: https://issues.apache.org/jira/browse/DBCP-209 Project: Commons Dbcp Issue Type: Bug Affects Versions: 1.2.1 Reporter: Michael Remijan Fix For: 1.3 In Tomcat's server.xml, I create a DataSource resource using the FACTORY org.apache.commons.dbcp.BasicDataSourceFactory and I also provide a URL and a DRIVERCLASSNAME. However I do not provide USERNAME or PASSWORD because I want to use DataSource.getConnection(user, pass) in my application. When I call DataSource.getConnection(user, pass) I get the following exception, java.sql.SQLException: invalid arguments in call, which was unexpected. I dug into the source code for BasicDataSource and I found what I think is the source of the problem. First, the method getConnection(user, pass) call the createDataSource() method. The createDataSource() method creates a Properties object and tries to put the username and password into the properties object. However, because the server.xml file does contain a username or password, this Properties object (named connectionProperties in the code) is empty. The createDataSource() the proceeds to call the validateConnectionFactory() method. This method then tries to get a Connection object!! This attempt fails because the Properties object has no username or password in it hence the Oracle driver complains about being passed invalid arguments. My question is why is the code working this way? Why does the createDataSource() and validateConnectionFactory() methods assume the username and password have been set in server.xml and then attempt to try to return a Connection object with the username and password passed to the getConnection(user, pass) method? It would seem to me the createDataSource() and validateConnectionFactory() methods should be aware of the username and password passed to the getConnection(user, pass) if this method is used. -- 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: (BEANUTILS-290) Merge Bean-Collections back into core BeanUtils and remove Bean-Collections sub-project
[ https://issues.apache.org/jira/browse/BEANUTILS-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niall Pemberton resolved BEANUTILS-290. --- Resolution: Fixed I have merged the classes and unit tests back into core BeanUtils and removed the bean-collections sub-module. Ant, Maven1 and Maven2 builds all work. Merge Bean-Collections back into core BeanUtils and remove Bean-Collections sub-project --- Key: BEANUTILS-290 URL: https://issues.apache.org/jira/browse/BEANUTILS-290 Project: Commons BeanUtils Issue Type: Task Components: Bean-Collections Affects Versions: 1.7.0 Reporter: Niall Pemberton Assignee: Niall Pemberton Priority: Minor Fix For: 1.8.0 This issue has been discussed in the following thread: http://tinyurl.com/2xdpku For BeanUtils 1.7.0 the following classes which had a dependency on Commons Collections were split into a separate bean-collections sub-module: BeanComparator.java BeanMap.java BeanPredicate.java BeanPropertyValueChangeClosure.java BeanPropertyValueEqualsPredicate.java BeanToPropertyValueTransformer.java Three flavours of jars were released in 1.7.0 commons-beanutils.jar - containing all BeanUtils classes, including above bean-collections ones commons-beanutils-bean-collections.jar - containing just the above bean-collections classes commons-beanutils-core.jar - containing BeanUtils classes excluding above bean-collections ones BeanUtils 1.7.0 was created using ant and (I presume) the maven poms for the above artifacts were manually created - unfortunately with mistakes: 1) The pom for commons-beanutils.jar DOESN'T declare any Commons Collections dependency (which it has for the bean-collections classes) 2) The pom for commons-beanutils-core.jar DOES declare a Commons Collections dependency (which it doesn't actually have) The proposal for BeanUtils 1.8.0 (see http://tinyurl.com/2xdpku) is to merge the bean-collections classes back into core BeanUtils and get rid of the bean-collections sub-module - releasing just a single jar for BeanUtils and marking the Commons Collections dependency as optional in the maven pom (see http://tinyurl.com/2nm2bu). -- 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: r557808 - /jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/converters/AbstractArrayConverter.java
Author: niallp Date: Thu Jul 19 16:05:03 2007 New Revision: 557808 URL: http://svn.apache.org/viewvc?view=revrev=557808 Log: BEANUTILS-280 CLIRR identified a binary incompatibility Modified: jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/converters/AbstractArrayConverter.java Modified: jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/converters/AbstractArrayConverter.java URL: http://svn.apache.org/viewvc/jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/converters/AbstractArrayConverter.java?view=diffrev=557808r1=557807r2=557808 == --- jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/converters/AbstractArrayConverter.java (original) +++ jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/converters/AbstractArrayConverter.java Thu Jul 19 16:05:03 2007 @@ -99,7 +99,7 @@ /** * pModel object for string arrays./p */ -protected static final String[] strings = new String[0]; +protected static String[] strings = new String[0]; /** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (DBCP-53) [dbcp] commons dbcp does not supports Firebird DB.
[ https://issues.apache.org/jira/browse/DBCP-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514039 ] Dain Sundstrom commented on DBCP-53: I don't think this is a DBCP issue. My guess is your torque configuration is wrong, but I'm not torque expert. The org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS class has the following method: public void setDriver(String v) throws ClassNotFoundException { assertInitializationAllowed(); this.driver = v; // make sure driver is registered Class.forName(v); } Which can fail for two reasons. First, if any connections have already been allocated from the data source, the assertInitializationAllowed method will throw and IllegalStateException because the data source is already actively creating connections for a data base. The second place this method can fail is the call to Class.forName. In either case, I don't think it is a DBCP issue. I think we should close this as invalid, and if Torque team find a bug in DBCP, they can open a new issue. [dbcp] commons dbcp does not supports Firebird DB. -- Key: DBCP-53 URL: https://issues.apache.org/jira/browse/DBCP-53 Project: Commons Dbcp Issue Type: Bug Environment: Operating System: Windows XP Platform: PC Reporter: DMoL Fix For: 1.3 I'm trying to use Torque-3.2 with open-source Firebird DBMS, but simple example not works. Here is the log output: 15.03.2006 21:47:38 org.apache.torque.dsfactory.AbstractDataSourceFactory setProperty SEVERE: Property: driver value: org.firebirdsql.jdbc.FBDriver is not supported by DataSource: org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS -- 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-209) Is DataSource.getConnection(user, pass) working the way it is suppose to?
[ https://issues.apache.org/jira/browse/DBCP-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-209. -- Resolution: Invalid I agree with Dain. For BasicDataSource, the username and password are pool properties. Is DataSource.getConnection(user, pass) working the way it is suppose to? - Key: DBCP-209 URL: https://issues.apache.org/jira/browse/DBCP-209 Project: Commons Dbcp Issue Type: Bug Affects Versions: 1.2.1 Reporter: Michael Remijan Fix For: 1.3 In Tomcat's server.xml, I create a DataSource resource using the FACTORY org.apache.commons.dbcp.BasicDataSourceFactory and I also provide a URL and a DRIVERCLASSNAME. However I do not provide USERNAME or PASSWORD because I want to use DataSource.getConnection(user, pass) in my application. When I call DataSource.getConnection(user, pass) I get the following exception, java.sql.SQLException: invalid arguments in call, which was unexpected. I dug into the source code for BasicDataSource and I found what I think is the source of the problem. First, the method getConnection(user, pass) call the createDataSource() method. The createDataSource() method creates a Properties object and tries to put the username and password into the properties object. However, because the server.xml file does contain a username or password, this Properties object (named connectionProperties in the code) is empty. The createDataSource() the proceeds to call the validateConnectionFactory() method. This method then tries to get a Connection object!! This attempt fails because the Properties object has no username or password in it hence the Oracle driver complains about being passed invalid arguments. My question is why is the code working this way? Why does the createDataSource() and validateConnectionFactory() methods assume the username and password have been set in server.xml and then attempt to try to return a Connection object with the username and password passed to the getConnection(user, pass) method? It would seem to me the createDataSource() and validateConnectionFactory() methods should be aware of the username and password passed to the getConnection(user, pass) if this method is used. -- 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: (DBCP-97) setAutoCommit(true) when returning connection to the pool
[ https://issues.apache.org/jira/browse/DBCP-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514044 ] Dain Sundstrom commented on DBCP-97: Yes, this is correct. When auto commit is off, you have an open transaction with the database, so leaving auto commit off while a connection is idle in the pool is a bad idea. One note. The current passivate code has the following block: conn.clearWarnings(); if(!conn.getAutoCommit()) { conn.setAutoCommit(true); } Do we want the clearWarnings() after the potential autocommit change? setAutoCommit(true) when returning connection to the pool - Key: DBCP-97 URL: https://issues.apache.org/jira/browse/DBCP-97 Project: Commons Dbcp Issue Type: Bug Affects Versions: Nightly Builds Environment: Operating System: All Platform: All Reporter: Dirk Verbeeck Fix For: 1.3 From the Struts user list: [OT] RE: Stackoverflow after DB inactivity (MySQL reconnect problem) http://www.mail-archive.com/[EMAIL PROTECTED]/msg70196.html Giving a hint to the database driver that you don't need long running transactions makes sense. setAutoCommit(true) should be added to PoolableConnectionFactory.passivateObject -- 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: (BEANUTILS-280) Check binary compatibility is still good
[ https://issues.apache.org/jira/browse/BEANUTILS-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niall Pemberton updated BEANUTILS-280: -- Attachment: (was: CLIRR.txt) Check binary compatibility is still good Key: BEANUTILS-280 URL: https://issues.apache.org/jira/browse/BEANUTILS-280 Project: Commons BeanUtils Issue Type: Task Reporter: Henri Yandell Fix For: 1.8.0 Attachments: CLIRR.txt Clirr/jardiff/whatever. -- 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: (BEANUTILS-280) Check binary compatibility is still good
[ https://issues.apache.org/jira/browse/BEANUTILS-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niall Pemberton updated BEANUTILS-280: -- Attachment: CLIRR.txt Attach latest CLIRR report showing BeanUtils trunk is binary compatible with version 1.7.0 Check binary compatibility is still good Key: BEANUTILS-280 URL: https://issues.apache.org/jira/browse/BEANUTILS-280 Project: Commons BeanUtils Issue Type: Task Reporter: Henri Yandell Fix For: 1.8.0 Attachments: CLIRR.txt Clirr/jardiff/whatever. -- 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]
[Jakarta-commons Wiki] Update of VfsFaq by KenTanaka
Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta-commons Wiki for change notification. The following page has been changed by KenTanaka: http://wiki.apache.org/jakarta-commons/VfsFaq The comment on the change is: Added a question Is there a tutorial for VFS? -- = VFS - Frequently asked questions = + + == Is there a tutorial for VFS? == + todo: Add link(s) here to tutorials and example code. For example, at the moment I'm looking for an example of reading a tar file, and extracting and expanding gzip files inside that tar file. == How to enter ftp passive mode == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r557816 - /jakarta/commons/proper/beanutils/trunk/build.xml
Author: niallp Date: Thu Jul 19 16:39:01 2007 New Revision: 557816 URL: http://svn.apache.org/viewvc?view=revrev=557816 Log: Minor changes to ant build Modified: jakarta/commons/proper/beanutils/trunk/build.xml Modified: jakarta/commons/proper/beanutils/trunk/build.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/beanutils/trunk/build.xml?view=diffrev=557816r1=557815r2=557816 == --- jakarta/commons/proper/beanutils/trunk/build.xml (original) +++ jakarta/commons/proper/beanutils/trunk/build.xml Thu Jul 19 16:39:01 2007 @@ -201,7 +201,7 @@ overview=src/java/overview.html doctitle=lt;h1gt;${component.title} (Version ${component.version})lt;/h1gt; windowtitle=${component.title} (Version ${component.version}) - bottom=Copyright (c) 2001-2004 - Apache Software Foundation + bottom=Copyright (c) 2001-2007 - Apache Software Foundation classpath refid=compile.classpath/ /javadoc /target @@ -230,7 +230,7 @@ tofile=${build.home}/classes/META-INF/LICENSE.txt/ copy file=NOTICE.txt tofile=${build.home}/classes/META-INF/NOTICE.txt/ -jarjarfile=${dist.home}/commons-beanutils.jar +jarjarfile=${dist.home}/commons-beanutils-${component.version}.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] Commented: (DBCP-155) [dbcp] allow to set = 6 parameters to do non-global SSL
[ https://issues.apache.org/jira/browse/DBCP-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514053 ] Dain Sundstrom commented on DBCP-155: - DBCP has support for JDBC connection properties. The JSSE properties you list above are not JDBC properties, and must be set as Java system properties. Unfortunately, that is how the JSSE specification works. Any changes to JSSE are beyond the scope of DBCP. I suggest we close this as won't fix. [dbcp] allow to set = 6 parameters to do non-global SSL Key: DBCP-155 URL: https://issues.apache.org/jira/browse/DBCP-155 Project: Commons Dbcp Issue Type: Improvement Environment: Operating System: All Platform: Other Reporter: Ralf Hauser Priority: Minor Fix For: 1.3 to work with http://dev.mysql.com/doc/refman/5.1/en/cj-using-ssl.html, it should be possible to call DriverManager.getConnection() with properties to replace the below 4: -Djavax.net.ssl.keyStore=path_to_keystore_file -Djavax.net.ssl.keyStorePassword=* -Djavax.net.ssl.trustStore=path_to_truststore_file -Djavax.net.ssl.trustStorePassword=* futhermore, adding a property - useSSL and - requireSSL would also help. plus the socketFactory-Class I asked for before (COM-2747) -- 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: (DBCP-152) [DBCP] add a socketFactory attribute to BasicDataSource (to allow SSL thread-safe)
[ https://issues.apache.org/jira/browse/DBCP-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514054 ] Dain Sundstrom commented on DBCP-152: - DBCP supports JDBC standard properties, so if mysql ssl can be configured via JDBC properties, this already works. Unfortunately, it appears mysql ssl can not be configured this way, and this is effectively request for mysql specific features which are beyond the scope of DBCP. I suggest we close this as won't fix. [DBCP] add a socketFactory attribute to BasicDataSource (to allow SSL thread-safe) Key: DBCP-152 URL: https://issues.apache.org/jira/browse/DBCP-152 Project: Commons Dbcp Issue Type: Improvement Affects Versions: 1.2 Environment: Operating System: All Platform: Other Reporter: Ralf Hauser Priority: Minor Fix For: 1.3 An app that accesses 2 datasources at two different places with different security policies via SSL (different set of permitted ciphers) currently is out of luck (http://lists.mysql.com/java/8689). The basic datasource should be enhanced with String socketFactory = ; and the corresponding getter and setter method, etc. org.apache.commons.dbcp.DriverConnectionFactory.createConnection() could then hand-over this full className via its Properties argument to enable different SSL policies per datasource (so, since the application programmer doesn't have the thread under her control, I guess it should rather be called dataSource-safe). The jdbc driver implementation can then use this to take the appropriate socket factory when creating a connection. See also http://lists.mysql.com/java/8695 -- 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: (DBCP-110) [dbcp] DBCP removeAbandoned not working
[ https://issues.apache.org/jira/browse/DBCP-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dain Sundstrom updated DBCP-110: Summary: [dbcp] DBCP removeAbandoned not working (was: [dbcp] Problem reported at forum.java.sun.com) [dbcp] DBCP removeAbandoned not working --- Key: DBCP-110 URL: https://issues.apache.org/jira/browse/DBCP-110 Project: Commons Dbcp Issue Type: Bug Environment: Operating System: other Platform: Other Reporter: David Smiley Priority: Minor Fix For: 1.3 Read the details at the URL. It includes a fix, I think. http://forum.java.sun.com/thread.jspa?threadID=658047tstart=0 I think I've run across this bug too, a couple days ago. I'm not sure if it exactly the same issue but I got the same underlying exception: java.util.NoSuchElementException: Timeout waiting for idle object I'm using Atlantassian Confluence which is using DBCP. -- 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: (DBCP-207) DBCP 1.2.1 incompatible with Informix (driver doesn't support setReadOnly(...))
[ https://issues.apache.org/jira/browse/DBCP-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dain Sundstrom updated DBCP-207: Attachment: DBCP-207.patch Already fixed for PoolingDataSource, but PerUserDataSource and SharedPoolDataSource still always set this value. These data sources use a primitives for the read only, transaction isolation and auto commit default values so there is not way to see if the value was not set. This patch checks if the read-only and auto-commit values are already set before changing them which should setReadOnly from being called. DBCP 1.2.1 incompatible with Informix (driver doesn't support setReadOnly(...)) --- Key: DBCP-207 URL: https://issues.apache.org/jira/browse/DBCP-207 Project: Commons Dbcp Issue Type: Bug Affects Versions: 1.2.1 Environment: using the pooling driver component with an informix driver Reporter: Kimberly Baer Fix For: 1.3 Attachments: DBCP-207.patch I recieved an error using commons-dbcp-1.2.1.jar and ifxjdbc.jar for my informix driver: org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool exhausted at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:183) at java.sql.DriverManager.getConnection(DriverManager.java:539) at java.sql.DriverManager.getConnection(DriverManager.java:211) at ConnectionPoolingTest.main(ConnectionPoolingTest.java:105) Caused by: java.util.NoSuchElementException: Could not create a validated object, cause: Read only mode not supported at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:806) at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:175) I will look into the comment provided by Dirk in bug ID DBCP-127 (version 1.1), but it appears this bug still has an impact in the 1.2.1 version. If anyone has any other suggestions, they would be greatly appreciated. -- 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]
[DBCP] Remove primitive default values?
The PerUserDataSource and SharedPoolDataSource use primitives for the read only, transaction isolation and auto commit default values so there is not way to see if the value was set in the configuration. This means there is no way to allow the driver defaults to pass through like in the PoolingDataSource. In the future, should all of these default values be non-primitive so we do not set them unless explicitly set in the configuration? -dain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TRANSACTION-9) [transaction] Add full file management capabilities to the FileResourceManager
[ https://issues.apache.org/jira/browse/TRANSACTION-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514060 ] Jörg Heinicke commented on TRANSACTION-9: - Actually I'm not very keen to these lock methods at all, but if you think it's better to have them I'm ok with it. The only thing we should have in mind is to not invent a second JCP 170 aka JCR (Content Repository for Java). Actually I wonder how the JCR implementations do transactional file system access. Regarding the interface proposal: 1. setProperty() is probably supposed to return void. 2. Thinking about it a bit more I agree on read/writeStream(). Using those in bean style makes not much sense. 3. writeStream() should probably have boolean parameter append again. 4. I still don't like the createFile/Directory() stuff. Sounds like creating sub resources, so it should be at least createAsFile/Directory(). But having both makes not much sense. Isn't it more a question of implementation, e.g. FileResource and DirectoryResource. Then create() would be sufficient. Question: How to decide whether to create a directory or a file then? Might be moved to ResourceManager then. What about getResource() with additional enum type parameter? Or getDirectoryResource() and getFileResource()? Moving that difference to the ResourceManager increases the usability IMHO. WDYT? 5. Just an idea: getChildren() matches listFiles() in File - the latter providing filter mechanism. What about that? If we have Resource instead of File we would also have Resource(NameFilter) - and could provide default adapter implementation for File(Name)Filter. [transaction] Add full file management capabilities to the FileResourceManager -- Key: TRANSACTION-9 URL: https://issues.apache.org/jira/browse/TRANSACTION-9 Project: Commons Transaction Issue Type: Improvement Environment: Operating System: All Platform: All Reporter: Peter Fassev Assignee: Oliver Zeigermann Priority: Minor Fix For: 2.0 Attachments: filemanager.zip Hi, As stated in the doc the FileResourceManager is: A resource manager for streamable objects stored in a file system I agree, that this is a resource manager, but it could be easily extended, to support a full file management system. It will be very helpful to have additional methods like renameResource(), getResourceSize(), getResourceTime(), setResourceTime() etc. This are common file operations, which should be managed by the FileResourceManager. Further it will be very helpful to have (real) support for resource collections (folders). It will be necessary to distinguish between single resources (files) and collections (folders). Together, this features will enable a transactional access to any file based resources - for instance a document repository. Are there plans for such extensions and if not, will they actually fit in the goals of the transaction library? If not, please open the underlying structure, like the inner class TransactionContext, in order to add extensions the file management. For instance, it will be good to have a separate factory method, which creates the context. If you are interested in this proposal, I am ready to contribute to this project. I consider myself as an experienced java developer and I will be glad to help you. Best regards Peter Fassev -- 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]
[DBCP] Release 1.3 soon?
Are there any DBCP-1.3 release plans? Based on the JIRAs I think we are close to being ready to release. Are there any items that are planned but don't have JIRAs? -dain Here are some open JIRAs I think we can close: Fixed: DBCP-194 BasicDataSource.setLogWriter should not do createDataSource DBCP-102 setReadOnly setAutoCommit called too many times DBCP-97 setAutoCommit(true) when returning connection to the pool DBCP-212 PoolingDataSource closes physical connections Invalid: DBCP-209 Is DataSource.getConnection(user, pass) working the way it is suppose to? User should be using either SharedPoolDataSource or the PerUserPoolDataSource. DBCP-53 commons dbcp does not supports Firebird DB Torque bug or misconfiguration by user. Won't fix DBCP-115 allow to set = 6 parameters to do non-global SSL Request for mysql specific feature DBCP-152 add a socketFactory attribute to BasicDataSource (to allow SSL thread-safe) Request for mysql specific feature - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [transaction 2.0] stripping to its very core
Oliver Zeigermann oliver at zeigermann.de writes: I am proposing to strip Commons Transaction to its very core. Deleted: - no more XA classes: We really can not an implement an XA resource with the existing implementation Hi Oliver, reducing ctx to a core is a good idea. I only would not like to see the XA stuff been dropped completely. I think it's quite important for getting ctx sold. I have a second project in maven 2 sense in mind as commons jci does: http://marc.info/?l=jakarta-commons-devm=117571327222719w=4. So we would have commons-transaction.jar and a commons-transaction-xa.jar. WDYT? Joerg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (DBCP-150) [dbcp] BasicDataSource : setter for connectionProperties
[ https://issues.apache.org/jira/browse/DBCP-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dain Sundstrom updated DBCP-150: Attachment: DBCP-150.patch Implementation, java doc and test case [dbcp] BasicDataSource : setter for connectionProperties Key: DBCP-150 URL: https://issues.apache.org/jira/browse/DBCP-150 Project: Commons Dbcp Issue Type: Improvement Affects Versions: 1.2 Environment: Operating System: All Platform: All Reporter: Maarten Bosteels Priority: Minor Fix For: 1.3 Attachments: DBCP-150.patch Adding a javabean-style setter for connectionProperties would certainly ease the configuration of a BasicDataSource within a Dependency Injection framework (eg Spring). see: http://article.gmane.org/gmane.comp.java.springframework.user/6501/ Thanks, Maarten -- 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: (DBCP-225) getConnection / borrowObject fails with NullPointerException
[ https://issues.apache.org/jira/browse/DBCP-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dain Sundstrom updated DBCP-225: Attachment: DBCP-225.patch This patch checks for null returned from connection factory and throws an IllegalStateException. We may want to go with a SQLException instead. I don't think this will fix Alexei's problem, but at least will cause a fast failure instead of getting a strange hollow connection. Alternatively, if we just need to ask Oracle again for a connection, we could put a retry loop in the connection factory. getConnection / borrowObject fails with NullPointerException Key: DBCP-225 URL: https://issues.apache.org/jira/browse/DBCP-225 Project: Commons Dbcp Issue Type: Bug Affects Versions: 1.2.1, 1.2.2 Environment: Solaris 10, Oracle 10g RAC Reporter: Alexei Samonov Fix For: 1.3 Attachments: DBCP-225.patch We use dbcp PoolingDataSource in Solaris/Oracle 10g RAC environment and our getConnection calls fail sporadically with the following stack trace (1.2.1) Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool exhausted at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:103) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540) ... more Caused by: java.util.NoSuchElementException: Could not create a validated object, cause: null at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:806) at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95) ... 24 more This is definitely not a pool exhausted situation, it is just being reported as pool exhausted. Since NoSuchElementException that you use does not allow cause, only Exception message (null) is being printed. With some debugging I was able to recover the root exception: java.lang.NullPointerException at org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:268) at org.apache.commons.dbcp.PoolableConnectionFactory.activateObject(PoolableConnectionFactory.java:368) at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:786) at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540) ... Looks like it is trying to borrow/validate DelegatingConnection which delegate is null. Hoping to resolve the issue we upgraded to 1.2.2 but it did not help. Here is is an exception stack trace from 1.2.2: org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error Could not create a validated object, cause: null at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:104) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880) ... more Caused by: java.util.NoSuchElementException: Could not create a validated object, cause: null at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:871) at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96) ... 28 more We use the following dbcp properties: autoCommit=false readOnly=false maxActive=200 maxIdle=20 minIdle=10 minEvictableIdleIime=30 maxWait=200 accessToUnderlyingConnectionAllowed=true validationQuery=SELECT 1 FROM DUAL ConnectionCachingEnabled=true FastConnectionFailoverEnabled=true I could not find the existing reported dbcp/object pool bug but I see similar reports on the web, for example http://forum.java.sun.com/thread.jspa?threadID=713200messageID=4124915 -- 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: r557855 - in /jakarta/commons/proper/beanutils/trunk: build-other-jars.xml build.xml maven.xml pom.xml src/conf/
Author: niallp Date: Thu Jul 19 20:00:49 2007 New Revision: 557855 URL: http://svn.apache.org/viewvc?view=revrev=557855 Log: BEANUTILS-290 - add ant script to re-create the core and bean-collections jars Added: jakarta/commons/proper/beanutils/trunk/build-other-jars.xml (with props) Removed: jakarta/commons/proper/beanutils/trunk/src/conf/ Modified: jakarta/commons/proper/beanutils/trunk/build.xml jakarta/commons/proper/beanutils/trunk/maven.xml jakarta/commons/proper/beanutils/trunk/pom.xml Added: jakarta/commons/proper/beanutils/trunk/build-other-jars.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/beanutils/trunk/build-other-jars.xml?view=autorev=557855 == --- jakarta/commons/proper/beanutils/trunk/build-other-jars.xml (added) +++ jakarta/commons/proper/beanutils/trunk/build-other-jars.xml Thu Jul 19 20:00:49 2007 @@ -0,0 +1,108 @@ +!-- + 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. +-- +project name=Bean Utilities (Other jars) default=other-jars basedir=. + + +!-- +$Id$ +-- + + +!-- == Component Declarations -- + + + !-- The current version number of this component -- + property name=component.version value=/ + + !-- The base directory for compilation targets -- + property name=build.home value=target/ + + !-- The base directory for distribution targets -- + property name=dist.home value=dist/ + + !-- JDK versions -- + property name=maven.compile.sourcevalue=/ + property name=maven.compile.targetvalue=/ + + +!-- == Executable Targets -- + + target name=other-jars depends=core-jar,bean-collections-jar + /target + + target name=core-jar description=Create BeanUtils Core jar +mkdir dir=${dist.home}/ +mkdir dir=${build.home}/classes/META-INF/ +copy file=LICENSE.txt tofile=${build.home}/classes/META-INF/LICENSE.txt/ +copy file=NOTICE.txt tofile=${build.home}/classes/META-INF/NOTICE.txt/ +jar jarfile=${dist.home}/commons-beanutils-core-${component.version}.jar +manifest +attribute name=Specification-Title value=Commons BeanUtils Core/ +attribute name=Specification-Version value=${component.version}/ +attribute name=Specification-Vendor value=The Apache Software Foundation/ +attribute name=Implementation-Title value=Commons BeanUtils Core/ +attribute name=Implementation-Version value=${component.version}/ +attribute name=Implementation-Vendor value=The Apache Software Foundation/ +attribute name=Implementation-Vendor-Id value=org.apache/ +attribute name=X-Compile-Source-JDK value=${maven.compile.source}/ +attribute name=X-Compile-Target-JDK value=${maven.compile.target}/ +/manifest +fileset dir=${build.home}/classes +include name=**/*.class/ +include name=**/LICENSE.txt/ +include name=**/NOTICE.txt/ +exclude name=**/BeanComparator*.class/ +exclude name=**/BeanMap*.class/ +exclude name=**/BeanPredicate*.class/ +exclude name=**/BeanPropertyValueChangeClosure*.class/ +exclude name=**/BeanPropertyValueEqualsPredicate*.class/ +exclude name=**/BeanToPropertyValueTransformer*.class/ +/fileset +/jar + /target + + target name=bean-collections-jar description=Create Bean Collections jar +mkdir dir=${dist.home}/ +mkdir dir=${build.home}/classes/META-INF/ +copy file=LICENSE.txt tofile=${build.home}/classes/META-INF/LICENSE.txt/ +copy file=NOTICE.txt tofile=${build.home}/classes/META-INF/NOTICE.txt/ +jar jarfile=${dist.home}/commons-beanutils-bean-collections-${component.version}.jar +manifest +attribute name=Specification-Title value=Commons BeanUtils Bean Collections/ +attribute name=Specification-Version value=${component.version}/ +attribute name=Specification-Vendor value=The Apache Software Foundation/ +
svn commit: r557857 - /jakarta/commons/proper/beanutils/trunk/maven.xml
Author: niallp Date: Thu Jul 19 20:16:55 2007 New Revision: 557857 URL: http://svn.apache.org/viewvc?view=revrev=557857 Log: BEANUTILS-290 - Include the other jars in the m1 distribution Modified: jakarta/commons/proper/beanutils/trunk/maven.xml Modified: jakarta/commons/proper/beanutils/trunk/maven.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/beanutils/trunk/maven.xml?view=diffrev=557857r1=557856r2=557857 == --- jakarta/commons/proper/beanutils/trunk/maven.xml (original) +++ jakarta/commons/proper/beanutils/trunk/maven.xml Thu Jul 19 20:16:55 2007 @@ -27,13 +27,13 @@ /copy /preGoal -preGoal name=jar:jar +postGoal name=jar:jar ant:ant antfile=build-other-jars.xml target=other-jars property name=component.version value=${pom.currentVersion}/ property name=build.homevalue=${maven.build.dir}/ property name=dist.home value=${maven.build.dir}/ /ant:ant -/preGoal +/postGoal !-- == -- !-- Copy into the binary distribution -- @@ -44,6 +44,8 @@ copy todir=${maven.dist.bin.assembly.dir} fileset file=${basedir}/NOTICE.txt/ fileset file=${basedir}/RELEASE-NOTES.txt/ + fileset file=${maven.build.dir}/commons-beanutils-core*.jar/ + fileset file=${maven.build.dir}/commons-beanutils-bean-collections*.jar/ /copy /postGoal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r557864 - in /jakarta/commons/proper/beanutils/trunk: NOTICE.txt maven.xml src/main/assembly/src.xml xdocs/building.xml xdocs/downloads.xml xdocs/navigation.xml
Author: niallp Date: Thu Jul 19 21:51:08 2007 New Revision: 557864 URL: http://svn.apache.org/viewvc?view=revrev=557864 Log: Build and site improvements Removed: jakarta/commons/proper/beanutils/trunk/xdocs/downloads.xml Modified: jakarta/commons/proper/beanutils/trunk/NOTICE.txt jakarta/commons/proper/beanutils/trunk/maven.xml jakarta/commons/proper/beanutils/trunk/src/main/assembly/src.xml jakarta/commons/proper/beanutils/trunk/xdocs/building.xml jakarta/commons/proper/beanutils/trunk/xdocs/navigation.xml Modified: jakarta/commons/proper/beanutils/trunk/NOTICE.txt URL: http://svn.apache.org/viewvc/jakarta/commons/proper/beanutils/trunk/NOTICE.txt?view=diffrev=557864r1=557863r2=557864 == --- jakarta/commons/proper/beanutils/trunk/NOTICE.txt (original) +++ jakarta/commons/proper/beanutils/trunk/NOTICE.txt Thu Jul 19 21:51:08 2007 @@ -1,5 +1,5 @@ Apache Commons BeanUtils -Copyright 2001-2006 The Apache Software Foundation +Copyright 2001-2007 The Apache Software Foundation This product includes software developed by The Apache Software Foundation (http://www.apache.org/). Modified: jakarta/commons/proper/beanutils/trunk/maven.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/beanutils/trunk/maven.xml?view=diffrev=557864r1=557863r2=557864 == --- jakarta/commons/proper/beanutils/trunk/maven.xml (original) +++ jakarta/commons/proper/beanutils/trunk/maven.xml Thu Jul 19 21:51:08 2007 @@ -40,6 +40,20 @@ !-- == -- postGoal name=dist:prepare-bin-filesystem +!-- Create a jar file containing the sources -- +jar destfile=${maven.dist.bin.assembly.dir}/${maven.final.name}-sources.jar +zipfileset prefix=META-INF dir=${basedir} +includes=LICENSE*, NOTICE*/ +fileset dir=${basedir}/src/java includes=**/*.java/ +/jar + +!-- Create a jar file containing the Javadocs -- +jar destfile=${maven.dist.bin.assembly.dir}/${maven.final.name}-javadoc.jar +zipfileset prefix=META-INF dir=${basedir} +includes=LICENSE*, NOTICE*/ +fileset dir=${basedir}/target/docs/apidocs/ +/jar + !-- Copy the NOTICE -- copy todir=${maven.dist.bin.assembly.dir} fileset file=${basedir}/NOTICE.txt/ @@ -57,6 +71,10 @@ !-- Copy the NOTICE -- copy todir=${maven.dist.src.assembly.dir} + fileset file=${basedir}/build-other-jars.xml/ + fileset file=${basedir}/checkstyle.xml/ + fileset file=${basedir}/license-header.txt/ + fileset file=${basedir}/pom.xml/ fileset file=${basedir}/NOTICE.txt/ fileset file=${basedir}/RELEASE-NOTES.txt/ fileset file=${basedir}/build.properties.sample/ @@ -74,10 +92,44 @@ !-- == -- postGoal name=dist + !-- Create a versioned pom -- + copy file=${basedir}/project.xml tofile=${maven.dist.dir}/${maven.final.name}.pom/ + + !-- create checksum for pom -- + ant:checksum file=${maven.dist.dir}/${maven.final.name}.pom property=pom.md5/ + ant:echo message=${pom.md5} *${maven.final.name}.pom + file=${maven.dist.dir}/${maven.final.name}.pom.md5 / + + copy todir=${maven.dist.dir} + fileset file=${maven.dist.bin.assembly.dir}/commons-beanutils*.jar/ + /copy + !-- create checksum for jar -- - ant:checksum file=${maven.build.dir}/${maven.final.name}.jar property=jar.md5/ + ant:checksum file=${maven.dist.dir}/${maven.final.name}.jar property=jar.md5/ ant:echo message=${jar.md5} *${maven.final.name}.jar - file=${maven.build.dir}/${maven.final.name}.jar.md5 / + file=${maven.dist.dir}/${maven.final.name}.jar.md5 / + + !-- create checksum for core jar -- + ant:checksum file=${maven.dist.dir}/commons-beanutils-core-${pom.currentVersion}.jar +property=core.jar.md5/ + ant:echo message=${core.jar.md5} *commons-beanutils-core-${pom.currentVersion}.jar + file=${maven.dist.dir}/commons-beanutils-core-${pom.currentVersion}.jar.md5 / + + !-- create checksum for bean-collections jar -- + ant:checksum file=${maven.dist.dir}/commons-beanutils-bean-collections-${pom.currentVersion}.jar +property=bean.collections.jar.md5/ + ant:echo message=${bean.collections.jar.md5} *commons-beanutils-bean-collections-${pom.currentVersion}.jar + file=${maven.dist.dir}/commons-beanutils-bean-collections-${pom.currentVersion}.jar.md5 / + + !-- create checksum for
svn commit: r557868 - /jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/ConvertUtilsBean.java
Author: niallp Date: Thu Jul 19 22:22:19 2007 New Revision: 557868 URL: http://svn.apache.org/viewvc?view=revrev=557868 Log: Only expose one new register method to the public API Modified: jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/ConvertUtilsBean.java Modified: jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/ConvertUtilsBean.java URL: http://svn.apache.org/viewvc/jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/ConvertUtilsBean.java?view=diffrev=557868r1=557867r2=557868 == --- jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/ConvertUtilsBean.java (original) +++ jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/ConvertUtilsBean.java Thu Jul 19 22:22:19 2007 @@ -583,16 +583,7 @@ } /** - * Register the standard converters with the specified defaults. - * /p - * This method delegates to the following methods (see their docs - * to find out which converters each one registers. - * ul - * li[EMAIL PROTECTED] ConvertUtilsBean#registerPrimitives(boolean)}/li - * li[EMAIL PROTECTED] ConvertUtilsBean#registerStandard(boolean, boolean)}/li - * li[EMAIL PROTECTED] ConvertUtilsBean#registerOther(boolean)}/li - * li[EMAIL PROTECTED] ConvertUtilsBean#registerArrays(boolean, int)}/li - * /ul + * Register the provided converters with the specified defaults. * * @param throwException codetrue/code if the converters should * throw an exception when a conversion error occurs, otherwise code @@ -602,8 +593,9 @@ * should use a default value of codenull/code, otherwise codefalse/code. * N.B. This values is ignored if codethrowException/code is codetrue/code * @param defaultArraySize The size of the default array value for array converters - * (see [EMAIL PROTECTED] ConvertUtilsBean#registerArrays(boolean, int)}). - * N.B. This values is ignored if codethrowException/code is codetrue/code + * (N.B. This values is ignored if codethrowException/code is codetrue/code). + * Specifying a value less than zero causes a codenullcode value to be used for + * the default. */ public void register(boolean throwException, boolean defaultNull, int defaultArraySize) { registerPrimitives(throwException); @@ -630,7 +622,7 @@ * throw an exception when a conversion error occurs, otherwise code * codefalse/code if a default value should be used. */ -public void registerPrimitives(boolean throwException) { +private void registerPrimitives(boolean throwException) { register(Boolean.TYPE, throwException ? new BooleanConverter(): new BooleanConverter(Boolean.FALSE)); register(Byte.TYPE, throwException ? new ByteConverter() : new ByteConverter(ZERO)); register(Character.TYPE, throwException ? new CharacterConverter() : new CharacterConverter(SPACE)); @@ -666,7 +658,7 @@ * should use a default value of codenull/code, otherwise codefalse/code. * N.B. This values is ignored if codethrowException/code is codetrue/code */ -public void registerStandard(boolean throwException, boolean defaultNull) { +private void registerStandard(boolean throwException, boolean defaultNull) { Number defaultNumber = defaultNull ? null : ZERO; BigDecimal bigDecDeflt = defaultNull ? null : new BigDecimal(0.0); @@ -707,7 +699,7 @@ * throw an exception when a conversion error occurs, otherwise code * codefalse/code if a default value should be used. */ -public void registerOther(boolean throwException) { +private void registerOther(boolean throwException) { register(Class.class, throwException ? new ClassConverter() : new ClassConverter(null)); register(java.util.Date.class, throwException ? new DateConverter() : new DateConverter(null)); register(Calendar.class, throwException ? new CalendarConverter() : new CalendarConverter(null)); @@ -729,7 +721,7 @@ * Specifying a value less than zero causes a codenullcode value to be used for * the default. */ -public void registerArrays(boolean throwException, int defaultArraySize) { +private void registerArrays(boolean throwException, int defaultArraySize) { // Primitives registerArrayConverter(Boolean.TYPE, new BooleanConverter(), throwException, defaultArraySize); - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r557869 - in /jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/locale: LocaleConvertUtils.java LocaleConvertUtilsBean.java
Author: niallp Date: Thu Jul 19 22:23:04 2007 New Revision: 557869 URL: http://svn.apache.org/viewvc?view=revrev=557869 Log: Deprecate method which expose FastHashMap in the public API Modified: jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/locale/LocaleConvertUtils.java jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/locale/LocaleConvertUtilsBean.java Modified: jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/locale/LocaleConvertUtils.java URL: http://svn.apache.org/viewvc/jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/locale/LocaleConvertUtils.java?view=diffrev=557869r1=557868r2=557869 == --- jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/locale/LocaleConvertUtils.java (original) +++ jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/locale/LocaleConvertUtils.java Thu Jul 19 22:23:04 2007 @@ -324,6 +324,7 @@ * @return The FastHashMap instance contains the all [EMAIL PROTECTED] LocaleConverter} types for * the specified locale. * @see LocaleConvertUtilsBean#lookup(Locale) + * @deprecated This method will be modified to return a Map in the next release. */ protected static FastHashMap lookup(Locale locale) { return LocaleConvertUtilsBean.getInstance().lookup(locale); @@ -338,6 +339,7 @@ * @return The FastHashMap instance contains the all [EMAIL PROTECTED] LocaleConverter} types * for the specified locale. * @see LocaleConvertUtilsBean#create(Locale) + * @deprecated This method will be modified to return a Map in the next release. */ protected static FastHashMap create(Locale locale) { Modified: jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/locale/LocaleConvertUtilsBean.java URL: http://svn.apache.org/viewvc/jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/locale/LocaleConvertUtilsBean.java?view=diffrev=557869r1=557868r2=557869 == --- jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/locale/LocaleConvertUtilsBean.java (original) +++ jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/locale/LocaleConvertUtilsBean.java Thu Jul 19 22:23:04 2007 @@ -424,6 +424,7 @@ * @param locale The Locale * @return The FastHashMap instance contains the all [EMAIL PROTECTED] LocaleConverter} types for * the specified locale. + * @deprecated This method will be modified to return a Map in the next release. */ protected FastHashMap lookup(Locale locale) { FastHashMap localeConverters; @@ -449,6 +450,7 @@ * @param locale The Locale * @return The FastHashMap instance contains the all [EMAIL PROTECTED] LocaleConverter} types * for the specified locale. + * @deprecated This method will be modified to return a Map in the next release. */ protected FastHashMap create(Locale locale) { - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 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/c
Sorry I missed this in initial review. I am not sure we want to remove the passivate() below, since that closes statements traced by this connection. Am I missing something here? Phil 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; +} +} } - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (BEANUTILS-280) Check binary compatibility is still good
[ https://issues.apache.org/jira/browse/BEANUTILS-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niall Pemberton resolved BEANUTILS-280. --- Resolution: Fixed Assignee: Niall Pemberton Check binary compatibility is still good Key: BEANUTILS-280 URL: https://issues.apache.org/jira/browse/BEANUTILS-280 Project: Commons BeanUtils Issue Type: Task Reporter: Henri Yandell Assignee: Niall Pemberton Fix For: 1.8.0 Attachments: CLIRR.txt Clirr/jardiff/whatever. -- 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] Remove primitive default values?
On 7/19/07, Dain Sundstrom [EMAIL PROTECTED] wrote: The PerUserDataSource and SharedPoolDataSource use primitives for the read only, transaction isolation and auto commit default values so there is not way to see if the value was set in the configuration. This means there is no way to allow the driver defaults to pass through like in the PoolingDataSource. In the future, should all of these default values be non-primitive so we do not set them unless explicitly set in the configuration? +1 Phil -dain - 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: r557873 - /jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/LazyDynaBean.java
Author: niallp Date: Thu Jul 19 22:36:28 2007 New Revision: 557873 URL: http://svn.apache.org/viewvc?view=revrev=557873 Log: Check the DynaProperty content type for List properties Modified: jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/LazyDynaBean.java Modified: jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/LazyDynaBean.java URL: http://svn.apache.org/viewvc/jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/LazyDynaBean.java?view=diffrev=557873r1=557872r2=557873 == --- jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/LazyDynaBean.java (original) +++ jakarta/commons/proper/beanutils/trunk/src/java/org/apache/commons/beanutils/LazyDynaBean.java Thu Jul 19 22:36:28 2007 @@ -598,7 +598,12 @@ List list = (List)indexedProperty; while (index = list.size()) { -list.add(null); +Class contentType = getDynaClass().getDynaProperty(name).getContentType(); +Object value = null; +if (contentType != null) { +value = createProperty(name+[+list.size()+], contentType); +} +list.add(value); } } @@ -631,6 +636,9 @@ * @return The new value */ protected Object createProperty(String name, Class type) { +if (type == null) { +return null; +} // Create Lists, arrays or DynaBeans if (type.isArray() || List.class.isAssignableFrom(type)) { - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jakarta/apache email subscription
Look at the headers of the email messages you receive and check out the Return-Path: line. That should tell you which address was used to subscribe to the mailing list, and hence help you unsubscribe. On 7/20/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm tired of getting all these emails and cannot get unsubscribed from this list! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- dIon Gillard Rule #131 of Acquisition: Information is Profit.