[jira] Updated: (CLI-51) [cli] Parameter value -something misinterpreted as a parameter
[
https://issues.apache.org/jira/browse/CLI-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Egge updated CLI-51:
--
Attachment: CL51.patch
Fix so parser doesn't burst options which are not defined. (-s) in the above
case.
Includes unit test.
[cli] Parameter value -something misinterpreted as a parameter
Key: CLI-51
URL: https://issues.apache.org/jira/browse/CLI-51
Project: Commons CLI
Issue Type: Bug
Components: CLI-1.x
Affects Versions: Nightly Builds
Environment: Operating System: Windows NT
Platform: PC
Reporter: Nigel King
Priority: Critical
Fix For: 1.1
Attachments: CL51.patch
If a parameter value is passed that contains a hyphen as the (delimited)
first
character, CLI parses this a parameter. For example using the call
java myclass -t -something
Results in the parser creating the invalid parameter -o (noting that it is
skipping the 's')
My code is using the Posix parser as follows
Options options = buildCommandLineOptions();
CommandLineParser parser = new PosixParser();
CommandLine commandLine = null;
try {
commandLine = parser.parse(options, args);
}
catch (ParseException e) {
System.out.println(Invalid parameters. + e.getMessage() + NEW_LINE);
System.exit(EXIT_CODE_ERROR);
}
This has been tested against the nightly build dated 20050503.
--
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: (CLI-129) CLI_1_BRANCH build.xml doesn't work
[ https://issues.apache.org/jira/browse/CLI-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Egge updated CLI-129: --- Attachment: AllTestSuite.java Test suite which runs all tests. Useful for IDEs. CLI_1_BRANCH build.xml doesn't work --- Key: CLI-129 URL: https://issues.apache.org/jira/browse/CLI-129 Project: Commons CLI Issue Type: Bug Components: CLI-1.x Affects Versions: 1.1 Environment: Ant 1.6.5 Reporter: Brian Egge Fix For: 1.1 Attachments: AllTestSuite.java, build.xml.patch This file was apparently created half-way through the CLI-2 branch. I removed the second 'jar' task, and fix up a couple other. -- 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]
A problem creating Java VM using JNI_CreateJavaVM
Hi,
I tried to change to prunsrv.c code so that after it fails creating a JVM
due to heap problem it will try again using a lower -Xmx parameter.
I have a problem doing it since after the first JVM creation failure, it
fails in all subsequent calls, specifically:
I tried to create it with -Xmx1700m and failed on a heap size problem (As
expected), right after that failure I change the -Xmx parameter to -Xmx800
(Which is expected to succeed) and try to create it again - And here I get a
failure again (Just a failure, no indication on heap size problem).
(Needless to say, when I try to create it with -Xmx800m from the first place
it succeeds).
The code change I did is at javajni.c at apxJavaInitialize (I know it looks
a bit hard-coded, its just for demo simplicity...):
if (DYNLOAD_FPTR(JNI_CreateJavaVM)((lpJava-lpJvm),
(void **)(lpJava-lpEnv),
vmArgs) != JNI_OK)
{
apxLogWrite(APXLOG_MARK_ERROR CreateJavaVM Failed);
wsprintfA(iB[1], -Xmx800m);
lpJvmOptions[XMX_OPTION].optionString = iB[1];
vmArgs.options = lpJvmOptions;
if (DYNLOAD_FPTR(JNI_CreateJavaVM)((lpJava-lpJvm),
(void
**)(lpJava-lpEnv),
vmArgs) != JNI_OK)
{
apxLogWrite(APXLOG_MARK_ERROR CreateJavaVM Failed
Again!!!);
}
rv = FALSE;
}
As I said before, the first call is with -Xmx1700 (This is the default
conifguration of the service) and it fails on heap size allocation, but the
second call is with -Xmx800, and it should succeed. The second call also
fails (Not on heap size problem, it simply fails...)
I don't know what the problem is, I suspect it has something to do with
cleanups after the first failure, but I could not get it to work.
Any one have a solution?
Re: Dbcp // Validation query timeout
Hi Adam,
Funny you should ask... I have recently been wondering that exact same
thing. In my case, a very, very slow validation query (approx 1.7
hours!) was causing Tomcat to crash. All 150 Tomcat worker threads were
eventually consumed, waiting for DBCP to return a connection.
Now, I have no idea why the database (Oracle 10g) was so thoroughly
wedged; I have yet to investigate that side of it. I had a look around
the DBCP code, though, and found two things: 1) there is no facility for
a validation time-out, and; 2) the validation query is executed /within
a synchronized block/ on the connection pool. This is in violation of
the design principals described in Joshua Bloch's Effective Java, Item
49, and is an excellent example of why Bloch is right on the money. In
this case, any client that wants a connection is forced to wait until
the pool validates the connections for all previous clients.
For this reason, I believe that the existing design of DBCP is flawed.
The validation query facility built into classes such as BasicDataSource
should not be used. Instead, any validation query should be executed
/after/ the connection is obtained from the connection pool.
To achieve this, I developed the ValidatingDataSource, below. This
class is a wrapper around a PoolingDataSource, that overrides
getConnection(). It also provides accessors for the validation query and
the validation query time-out. When the client calls getConnection(),
the ValidatingDataSource obtains a connection from the PoolingDataSource
and invokes the validation query on it. If the query succeeds, the
connection is return to the client. If it fails, or times-out, the
connection is removed from the pool, and another connection obtained.
This process continues indefinitely; some sort of limit would be a good
idea, and I'll implement one Real Soon Now.
I have also created a BetterDataSource class, that extends
BasicDataSource to use the ValidatingDataSource. However, the name
BetterDataSource is rather pretentious and I'm too embarrassed to list
the code here.
Regards,
Greg [EMAIL PROTECTED]
PS: I apologise for including this chunk of code in my reply. I really
should learn how to use the DBCP patch process...
/*
* ValidatingDataSource.java
*/
package com.greghhawkes.util.dbcp;
import java.io.PrintWriter;
import java.sql.Connection;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import javax.sql.DataSource;
import org.apache.commons.dbcp.DelegatingConnection;
import org.apache.commons.dbcp.PoolableConnection;
import org.apache.commons.dbcp.PoolingDataSource;
/**
* A data source wrapper that validates the connection returned by the
underlying PoolingDataSource.
* @author Greg Hawkes
*/
public class ValidatingDataSource implements javax.sql.DataSource {
private PoolingDataSource m_delegate;
private String m_validationQuery;
private int m_validationTimeout;
/**
* Creates a new instance of ValidatingDataSource
*/
public ValidatingDataSource(PoolingDataSource delegate) {
m_delegate = delegate;
}
/**
* Obtain and (optionally) validate a connection from the underlying
datasource.
*/
public Connection getConnection() throws SQLException {
m_delegate.setAccessToUnderlyingConnectionAllowed(true);
for ( ; ; ) {
Connection conn = m_delegate.getConnection();
if (conn == null) {
return null;
} else if (isValid(conn)) {
return conn;
}
// Validation failed; destroy the connection
DelegatingConnection dc = (DelegatingConnection) conn;
PoolableConnection c = (PoolableConnection) dc.getDelegate();
c.reallyClose();
}
}
public Connection getConnection(String username, String password)
throws SQLException {
throw new UnsupportedOperationException();
}
public PrintWriter getLogWriter() throws SQLException {
return m_delegate.getLogWriter();
}
public void setLogWriter(PrintWriter out) throws SQLException {
m_delegate.setLogWriter(out);
}
public void setLoginTimeout(int seconds) throws SQLException {
m_delegate.setLoginTimeout(seconds);
}
public int getLoginTimeout() throws SQLException {
return m_delegate.getLoginTimeout();
}
public String getValidationQuery() {
return m_validationQuery;
}
public void setValidationQuery(String validationQuery) {
m_validationQuery = validationQuery;
}
public int getValidationTimeout() {
return m_validationTimeout;
}
public void setValidationTimeout(int validationTimeout) {
if (validationTimeout 0) {
validationTimeout = 0;
}
m_validationTimeout = validationTimeout;
}
/**
* Test whether the validationQuery can be executed on the connection,
*/
Proposal and question for handling of constants
Hello! I've got one question and two proposals for commons validator! 1. Question: How can I get values for some constants out of the validator-framework? ValidatorResources.getConstants() unfortunately is protected! But I want to use the constants I defined somewhere else! 2. Proposal: What about making the above method public for this reason? 3. Proposal: It would really be nice, if I could set the constants using a java properties file! 4. Proposal: Am I right, that I currently can only use the javascript validation when I click the submit button? What if I want to validate a field when the focus leaves this field? Thanks a lot in advance! Florian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dbcp // Validation query timeout
On 5/11/07, Tworkiewicz, Adam [EMAIL PROTECTED] wrote: Hi, We use dbcp for connection pooling in our application that talks to Oracle 10g RAC (2 nodes). Our dbcp config is attached below. We are seeing undesired behaviour when we test db failover. Since we use load balancing connections in the pool point to both db servers. When we shutdown one of the db nodes our ping query hangs waiting for TCP/IP traffic. Since the box is down there is no traffic and the query hangs until a TCP/IP timeout occures. Is there a way to set up a timeout on the validation query? Currently, there is no way to do that. Would you mind opening JIRA ticket requesting this feature? You can do that here: http://jakarta.apache.org/commons/dbcp/issue-tracking.html Patches welcome. Phil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dbcp // Validation query timeout
On 5/11/07, Greg Hawkes [EMAIL PROTECTED] wrote: Hi Adam, Funny you should ask... I have recently been wondering that exact same thing. In my case, a very, very slow validation query (approx 1.7 hours!) was causing Tomcat to crash. All 150 Tomcat worker threads were eventually consumed, waiting for DBCP to return a connection. Just so I understand the use case here, is this something that happens every n queries, or does the database just periodically slow down uniformly, so all queries are slow? Also, what versions of commons dbcp and commons pool are you running? Now, I have no idea why the database (Oracle 10g) was so thoroughly wedged; I have yet to investigate that side of it. I had a look around the DBCP code, though, and found two things: 1) there is no facility for a validation time-out, and; 2) the validation query is executed /within a synchronized block/ on the connection pool. This is in violation of the design principals described in Joshua Bloch's Effective Java, Item 49, and is an excellent example of why Bloch is right on the money. In this case, any client that wants a connection is forced to wait until the pool validates the connections for all previous clients. For this reason, I believe that the existing design of DBCP is flawed. The validation query facility built into classes such as BasicDataSource should not be used. Instead, any validation query should be executed /after/ the connection is obtained from the connection pool. These are valid points. Please open JIRA tickets and make suggestions for improvement in the tickets and discussion on commons-dev. Patches are welcome. The core design issue is in commons pool's GenericObjectPool (GOP), which arguably violates Block's principle above in order to ensure thread safety in its 1.x design. Work on a 2.0 version of pool has begun and discussion of this and other topics is welcome on the commons-dev mailing list. Version 1.3 of commons pool added synchronization to GOP to deal with thread safety issues reported in POOL-26 and some other issues resolved in the 1.3 release. Unfortunately, this may have exacerbated the problem mentioned here. If you are using dbcp 1.2.2 and pool 1.3, you could fall back to pool 1.2 (still using dbcp 1.2.2); but in this case you should review the release notes for pool 1.3 to see what other bug fixes you would be missing: http://jakarta.apache.org/commons/pool/release-notes-1.3.html To achieve this, I developed the ValidatingDataSource, below. This class is a wrapper around a PoolingDataSource, that overrides getConnection(). It also provides accessors for the validation query and the validation query time-out. When the client calls getConnection(), the ValidatingDataSource obtains a connection from the PoolingDataSource and invokes the validation query on it. If the query succeeds, the connection is return to the client. If it fails, or times-out, the connection is removed from the pool, and another connection obtained. This process continues indefinitely; some sort of limit would be a good idea, and I'll implement one Real Soon Now. I have also created a BetterDataSource class, that extends BasicDataSource to use the ValidatingDataSource. However, the name BetterDataSource is rather pretentious and I'm too embarrassed to list the code here. Regards, Greg [EMAIL PROTECTED] PS: I apologise for including this chunk of code in my reply. I really should learn how to use the DBCP patch process... Not a problem. To start, you could just add the sources for your new classes to a JIRA ticket. Make sure you can legally contribute them and for new classes its best to include the apache license header (cut and paste from any current source, or see http://www.apache.org/licenses/LICENSE-2.0.html#apply). Have a look at http://www.apache.org/dev/contributors.html http://jakarta.apache.org/commons/svninfo.html for more information about how to checkout sources from subversion and submit patches. Feel free to ask here or on commons-dev if you have problems getting set up. Thanks for the feedback and thanks in advance for your contributions. Phil - 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 9 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. -WARNING- Overriding Maven properties: [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties -INFO- Project Reports in: /usr/local/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: 17 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/commons-cli-1.0.x/target/commons-cli-13052007.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-13052007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13052007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13052007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13052007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13052007.jar:/usr/local/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
[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 9 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. -WARNING- Overriding Maven properties: [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties -INFO- Project Reports in: /usr/local/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: 17 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/commons-cli-1.0.x/target/commons-cli-13052007.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-13052007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13052007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13052007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13052007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13052007.jar:/usr/local/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
[EMAIL PROTECTED]: Project commons-jelly-tags-fmt-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-fmt-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 9 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-fmt-test : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -WARNING- Overriding Maven properties: [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/test-reports The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/gump_work/build_commons-jelly_commons-jelly-tags-fmt-test.html Work Name: build_commons-jelly_commons-jelly-tags-fmt-test (Type: Build) Work ended in a state of : Failed Elapsed: 11 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-commands-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-classpath-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-core-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-bsf-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-reflect-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-util-2.0b4.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/beanshell/target/commons-jelly-tags-beanshell-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-13052007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13052007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13052007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13052007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13052007.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/commons-jelly-tags-fmt-13052007.jar - [junit] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) [junit] at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) [junit] at java.net.URLClassLoader.access$100(URLClassLoader.java:56) [junit] at java.net.URLClassLoader$1.run(URLClassLoader.java:195) [junit] at java.security.AccessController.doPrivileged(Native Method) [junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:188) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:306) [junit] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:251) [junit] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) [junit] at org.apache.commons.jelly.tags.ant.AntTagLibrary.createProject(AntTagLibrary.java:128)
[EMAIL PROTECTED]: Project commons-jelly-tags-fmt-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-fmt-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 9 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-fmt-test : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -WARNING- Overriding Maven properties: [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/test-reports The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/gump_work/build_commons-jelly_commons-jelly-tags-fmt-test.html Work Name: build_commons-jelly_commons-jelly-tags-fmt-test (Type: Build) Work ended in a state of : Failed Elapsed: 11 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-commands-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-classpath-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-core-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-bsf-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-reflect-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-util-2.0b4.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/beanshell/target/commons-jelly-tags-beanshell-13052007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-13052007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13052007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-13052007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-13052007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13052007.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/commons-jelly-tags-fmt-13052007.jar - [junit] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) [junit] at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) [junit] at java.net.URLClassLoader.access$100(URLClassLoader.java:56) [junit] at java.net.URLClassLoader$1.run(URLClassLoader.java:195) [junit] at java.security.AccessController.doPrivileged(Native Method) [junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:188) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:306) [junit] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:251) [junit] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) [junit] at org.apache.commons.jelly.tags.ant.AntTagLibrary.createProject(AntTagLibrary.java:128)
Re: Proposal and question for handling of constants
On 5/13/07, Florian Rampp [EMAIL PROTECTED] wrote: Hello! I've got one question and two proposals for commons validator! 1. Question: How can I get values for some constants out of the validator-framework? ValidatorResources.getConstants() unfortunately is protected! But I want to use the constants I defined somewhere else! You could create your own implementation and expose the method as public. 2. Proposal: What about making the above method public for this reason? Possibly, open a Jira ticket and describe the use-case. 3. Proposal: It would really be nice, if I could set the constants using a java properties file! I don't see any benefit of this over the XML configuration - IMO will just add confusion. 4. Proposal: Am I right, that I currently can only use the javascript validation when I click the submit button? What if I want to validate a field when the focus leaves this field? Commons Validator provides nothing to invoke the JavaScript validations for a field - Struts does, but it doesn't handle field level validation - just forms as a whole. A couple of years back I worked on doing this, but never finished it off or added it to validator (so its probably not that likely yto happen) http://issues.apache.org/jira/browse/VALIDATOR-106 Niall Thanks a lot in advance! Florian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[math] Release planning, IOC-friendlyness
I think that modulo some cleanup, testing and review and the one dangling item below, we should be ready for a [math] release. I will RM if no one else wants to, but would appreciate it (and support by sharing gruntwork) if someone else volunteers. Here are some questions to resolve in the release plan: 1. Is this 1.2 or 2.0? There is so much in the added Mantissa classes that 2.0 makes sense from a functionality standpoint. On the other hand, we have not broken backward compatibility with anything (yet) and if we decide to go 2.0, we could consider some API change. My vote is to keep compatibility in place, but still name it 2.0. 2. What if anything should we add to make pluggability as designed in the library compatible with IOC frameworks? It won't work to add setters for the main factories, since we use the static getInstance factory pattern (see e.g. UnivariateRealSoverFactory). What might make more sense would be to add setters for the individual solvers in e.g. UnivariateRealSoverFactoryImpl. Any ideas on how best to attack this? For those not familiar with [math] who may have ideas, the basic setup is that we use abstract factories with static getInstance methods that return concrete factories looked up using commons-discovery. The concrete factories themselves source multiple different object types . Phil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r537699 - /jakarta/commons/proper/pool/trunk/xdocs/downloads.xml
Author: psteitz Date: Sun May 13 20:52:12 2007 New Revision: 537699 URL: http://svn.apache.org/viewvc?view=revrev=537699 Log: Added link to 1.3 release notes. Modified: jakarta/commons/proper/pool/trunk/xdocs/downloads.xml Modified: jakarta/commons/proper/pool/trunk/xdocs/downloads.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/pool/trunk/xdocs/downloads.xml?view=diffrev=537699r1=537698r2=537699 == --- jakarta/commons/proper/pool/trunk/xdocs/downloads.xml (original) +++ jakarta/commons/proper/pool/trunk/xdocs/downloads.xml Sun May 13 20:52:12 2007 @@ -26,6 +26,7 @@ section name=Releases pThe following releases are available:/p ul + liRelease 1.3 - 3 April 2006 - a href=release-notes-1.3.html(release notes)/a/li liRelease 1.2 - 7 June 2004 - a href=release-notes-1.2.html(release notes)/a/li liRelease 1.1 - 20 October 2003 - a href=release-notes-1.1.html(release notes)/a/li liRelease 1.0.1 - 12 August 2002/li - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r537699 - /jakarta/commons/proper/pool/trunk/xdocs/downloads.xml
The file release-notes-1.3.html is deployed on the pool web site, but there is no release-notes-1.3.xml in /xdocs. If someone (Sandy?) has this file locally, it should be added to svn. Otherwise, we should just add the html file to svn. Phil On 5/13/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Author: psteitz Date: Sun May 13 20:52:12 2007 New Revision: 537699 URL: http://svn.apache.org/viewvc?view=revrev=537699 Log: Added link to 1.3 release notes. Modified: jakarta/commons/proper/pool/trunk/xdocs/downloads.xml Modified: jakarta/commons/proper/pool/trunk/xdocs/downloads.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/pool/trunk/xdocs/downloads.xml?view=diffrev=537699r1=537698r2=537699 == --- jakarta/commons/proper/pool/trunk/xdocs/downloads.xml (original) +++ jakarta/commons/proper/pool/trunk/xdocs/downloads.xml Sun May 13 20:52:12 2007 @@ -26,6 +26,7 @@ section name=Releases pThe following releases are available:/p ul + liRelease 1.3 - 3 April 2006 - a href=release-notes-1.3.html(release notes)/a/li liRelease 1.2 - 7 June 2004 - a href=release-notes-1.2.html(release notes)/a/li liRelease 1.1 - 20 October 2003 - a href=release-notes-1.1.html(release notes)/a/li liRelease 1.0.1 - 12 August 2002/li - 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: r537700 - /jakarta/commons/proper/math/trunk/pom.xml
Author: psteitz Date: Sun May 13 21:19:48 2007 New Revision: 537700 URL: http://svn.apache.org/viewvc?view=revrev=537700 Log: Configured assembly plugin, bumped commons parent version to 2. Modified: jakarta/commons/proper/math/trunk/pom.xml Modified: jakarta/commons/proper/math/trunk/pom.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/math/trunk/pom.xml?view=diffrev=537700r1=537699r2=537700 == --- jakarta/commons/proper/math/trunk/pom.xml (original) +++ jakarta/commons/proper/math/trunk/pom.xml Sun May 13 21:19:48 2007 @@ -22,7 +22,7 @@ parent groupIdorg.apache.commons/groupId artifactIdcommons-parent/artifactId -version1/version +version2/version /parent modelVersion4.0.0/modelVersion groupIdcommons-math/groupId @@ -199,6 +199,16 @@ excludes exclude**/*AbstractTest.java/exclude /excludes + /configuration +/plugin +plugin + artifactIdmaven-assembly-plugin/artifactId + version2.2-beta-1/version + configuration +descriptors + descriptorsrc/assembly/src.xml/descriptor + descriptorsrc/assembly/bin.xml/descriptor +/descriptors /configuration /plugin /plugins - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r537701 - /jakarta/commons/proper/math/trunk/src/java/org/apache/commons/math/stat/descriptive/moment/Variance.java
Author: psteitz Date: Sun May 13 21:22:07 2007 New Revision: 537701 URL: http://svn.apache.org/viewvc?view=revrev=537701 Log: Javadoc only. Fixed typo. Modified: jakarta/commons/proper/math/trunk/src/java/org/apache/commons/math/stat/descriptive/moment/Variance.java Modified: jakarta/commons/proper/math/trunk/src/java/org/apache/commons/math/stat/descriptive/moment/Variance.java URL: http://svn.apache.org/viewvc/jakarta/commons/proper/math/trunk/src/java/org/apache/commons/math/stat/descriptive/moment/Variance.java?view=diffrev=537701r1=537700r2=537701 == --- jakarta/commons/proper/math/trunk/src/java/org/apache/commons/math/stat/descriptive/moment/Variance.java (original) +++ jakarta/commons/proper/math/trunk/src/java/org/apache/commons/math/stat/descriptive/moment/Variance.java Sun May 13 21:22:07 2007 @@ -32,7 +32,7 @@ * The definitional formula does not have good numerical properties, so * this implementation uses updating formulas based on West's algorithm * as described in a href=http://doi.acm.org/10.1145/359146.359152; - * Chan, T. F. andJ. G. Lewis 1979, iCommunications of the ACM/i, + * Chan, T. F. and J. G. Lewis 1979, iCommunications of the ACM/i, * vol. 22 no. 9, pp. 526-531./a. * p * The population variance ( sum((x_i - mean)^2) / n ) can also - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r537703 - /jakarta/commons/proper/math/trunk/xdocs/userguide/geometry.xml
Author: psteitz Date: Sun May 13 21:28:00 2007 New Revision: 537703 URL: http://svn.apache.org/viewvc?view=revrev=537703 Log: Fixed some typos, minor edits. Modified: jakarta/commons/proper/math/trunk/xdocs/userguide/geometry.xml Modified: jakarta/commons/proper/math/trunk/xdocs/userguide/geometry.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/math/trunk/xdocs/userguide/geometry.xml?view=diffrev=537703r1=537702r2=537703 == --- jakarta/commons/proper/math/trunk/xdocs/userguide/geometry.xml (original) +++ jakarta/commons/proper/math/trunk/xdocs/userguide/geometry.xml Sun May 13 21:28:00 2007 @@ -38,7 +38,7 @@ a href=../apidocs/org/apache/commons/math/geometry/Vector3D.html org.apache.commons.math.geometry.Vector3D/a provides a simple vector type. One important feature is that instances of this class are guaranteed - to be immutable, this greatly simplifies modelization of dynamical systems + to be immutable, this greatly simplifies modelling dynamical systems with changing states: once a vector has been computed, a reference to it is known to preserve its state as long as the reference itself is preserved. /p @@ -66,8 +66,8 @@ p Rotations can be represented by several different mathematical entities (matrices, axe and angle, Cardan or Euler angles, - quaternions). This class presents an higher level abstraction, more - user-oriented and hiding this implementation details. Well, for the + quaternions). This class presents a higher level abstraction, more + user-oriented and hiding implementation details. Well, for the curious, we use quaternions for the internal representation. The user can build a rotation from any of these representations, and any of these representations can be retrieved from a codeRotation/code @@ -83,7 +83,7 @@ /p sourcedouble[] angles = new Rotation(matrix, 1.0e-10).getAngles(RotationOrder.XYZ);/source p - Focus is oriented on what a rotation emdo/em rather than on its + Focus is oriented on what a rotation emdoes/em rather than on its underlying representation. Once it has been built, and regardless of its internal representation, a rotation is an emoperator/em which basically transforms three dimensional vectors into other three @@ -95,7 +95,7 @@ often consider the vectors are fixed (say the Earth direction for example) and the rotation transforms the coordinates coordinates of this vector in inertial frame into the coordinates of the same vector - in satellite frame. In this case, the rotation implicitely defines the + in satellite frame. In this case, the rotation implicitly defines the relation between the two frames (we have fixed vectors and moving frame). Another example could be a telescope control application, where the rotation would transform the sighting direction at rest into the desired - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (VFS-132) Attributes are case-senstive
Attributes are case-senstive Key: VFS-132 URL: https://issues.apache.org/jira/browse/VFS-132 Project: Commons VFS Issue Type: New Feature Affects Versions: 1.1 Reporter: Adam Heath Attachments: fix_attributes-are-case-sensitive.patch The set and list methods don't lowercase attribute names; why should get? -- 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: (VFS-132) Attributes are case-senstive
[ https://issues.apache.org/jira/browse/VFS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Heath updated VFS-132: --- Attachment: fix_attributes-are-case-sensitive.patch Against version svn 501759. Attributes are case-senstive Key: VFS-132 URL: https://issues.apache.org/jira/browse/VFS-132 Project: Commons VFS Issue Type: New Feature Affects Versions: 1.1 Reporter: Adam Heath Attachments: fix_attributes-are-case-sensitive.patch The set and list methods don't lowercase attribute names; why should get? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (VFS-133) Add RandomAccessMode.getModeString()
Add RandomAccessMode.getModeString() Key: VFS-133 URL: https://issues.apache.org/jira/browse/VFS-133 Project: Commons VFS Issue Type: New Feature Affects Versions: later Reporter: Adam Heath Priority: Trivial As $summary, that returns r, w, rw, or , as appropriate. -- 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: (VFS-133) Add RandomAccessMode.getModeString()
[ https://issues.apache.org/jira/browse/VFS-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Heath updated VFS-133: --- Attachment: feature_RandomAccessMode-getModeString.patch Against svn 501759. Add RandomAccessMode.getModeString() Key: VFS-133 URL: https://issues.apache.org/jira/browse/VFS-133 Project: Commons VFS Issue Type: New Feature Affects Versions: later Reporter: Adam Heath Priority: Trivial Attachments: feature_RandomAccessMode-getModeString.patch As $summary, that returns r, w, rw, or , as appropriate. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (VFS-134) Memory leak closing RandomAccessContent.
Memory leak closing RandomAccessContent. Key: VFS-134 URL: https://issues.apache.org/jira/browse/VFS-134 Project: Commons VFS Issue Type: Bug Affects Versions: 1.1 Reporter: Adam Heath Closing RandomAccessContent causes a memory leak, because the object is removed from the wrong container. -- 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: (VFS-134) Memory leak closing RandomAccessContent.
[ https://issues.apache.org/jira/browse/VFS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Heath updated VFS-134: --- Attachment: fix_ThreadData-remove-Random.patch Against svn 501759. Memory leak closing RandomAccessContent. Key: VFS-134 URL: https://issues.apache.org/jira/browse/VFS-134 Project: Commons VFS Issue Type: Bug Affects Versions: 1.1 Reporter: Adam Heath Attachments: fix_ThreadData-remove-Random.patch Closing RandomAccessContent causes a memory leak, because the object is removed from the wrong container. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (VFS-135) Don't force-set the classloader
Don't force-set the classloader --- Key: VFS-135 URL: https://issues.apache.org/jira/browse/VFS-135 Project: Commons VFS Issue Type: Bug Affects Versions: 1.1 Reporter: Adam Heath Priority: Minor Attachments: fix_StandardFileSystemManager-use-findClassLoader.patch StandardFileSystemManager is force-setting the classloader. The attached patch changes this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (VFS-135) Don't force-set the classloader
[ https://issues.apache.org/jira/browse/VFS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Heath updated VFS-135: --- Attachment: fix_StandardFileSystemManager-use-findClassLoader.patch Against svn 501759. Don't force-set the classloader --- Key: VFS-135 URL: https://issues.apache.org/jira/browse/VFS-135 Project: Commons VFS Issue Type: Bug Affects Versions: 1.1 Reporter: Adam Heath Priority: Minor Attachments: fix_StandardFileSystemManager-use-findClassLoader.patch StandardFileSystemManager is force-setting the classloader. The attached patch changes this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r537713 - /jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/DefaultFileContent.java
Author: imario
Date: Sun May 13 22:40:17 2007
New Revision: 537713
URL: http://svn.apache.org/viewvc?view=revrev=537713
Log:
VFS-132: Thanks to Adam Heath for pointing out
Modified:
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/DefaultFileContent.java
Modified:
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/DefaultFileContent.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/DefaultFileContent.java?view=diffrev=537713r1=537712r2=537713
==
---
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/DefaultFileContent.java
(original)
+++
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/DefaultFileContent.java
Sun May 13 22:40:17 2007
@@ -238,10 +238,12 @@
throws FileSystemException
{
getAttributes();
+ /* [EMAIL PROTECTED]: VFS-132 since I do not know why I've done
this, I'll disable it again
if (attrs.containsKey(attrName))
{
return attrs.get(attrName);
}
+ */
return attrs.get(attrName.toLowerCase());
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (VFS-132) Attributes are case-senstive
[ https://issues.apache.org/jira/browse/VFS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Ivankovits resolved VFS-132. -- Resolution: Fixed Fix Version/s: 1.1 yep .. I've no clue why I've done it ... should have written a comment ... damn. Since it is not clear what the benefit of this code could be I've disabled it as suggested. Thanks! Attributes are case-senstive Key: VFS-132 URL: https://issues.apache.org/jira/browse/VFS-132 Project: Commons VFS Issue Type: New Feature Affects Versions: 1.1 Reporter: Adam Heath Fix For: 1.1 Attachments: fix_attributes-are-case-sensitive.patch The set and list methods don't lowercase attribute names; why should get? -- 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: r537714 - in /jakarta/commons/proper/vfs/trunk: core/src/main/java/org/apache/commons/vfs/provider/local/ core/src/main/java/org/apache/commons/vfs/util/ sandbox/src/main/java/org/apache/c
Author: imario
Date: Sun May 13 22:51:00 2007
New Revision: 537714
URL: http://svn.apache.org/viewvc?view=revrev=537714
Log:
VFS-133: added RandomAccessMode.getModeString - Thanks to Adam Heath for the
patch
Modified:
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/local/LocalFileRandomAccessContent.java
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/util/RandomAccessMode.java
jakarta/commons/proper/vfs/trunk/sandbox/src/main/java/org/apache/commons/vfs/provider/smb/SmbFileRandomAccessContent.java
Modified:
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/local/LocalFileRandomAccessContent.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/local/LocalFileRandomAccessContent.java?view=diffrev=537714r1=537713r2=537714
==
---
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/local/LocalFileRandomAccessContent.java
(original)
+++
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/local/LocalFileRandomAccessContent.java
Sun May 13 22:51:00 2007
@@ -43,19 +43,9 @@
{
super(mode);
-StringBuffer modes = new StringBuffer(2);
-if (mode.requestRead())
-{
-modes.append('r');
-}
-if (mode.requestWrite())
-{
-modes.append('w');
-}
-
try
{
-raf = new RandomAccessFile(localFile, modes.toString());
+raf = new RandomAccessFile(localFile, mode.getModeString());
rafis = new InputStream()
{
public int read() throws IOException
Modified:
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/util/RandomAccessMode.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/util/RandomAccessMode.java?view=diffrev=537714r1=537713r2=537714
==
---
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/util/RandomAccessMode.java
(original)
+++
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/util/RandomAccessMode.java
Sun May 13 22:51:00 2007
@@ -24,33 +24,54 @@
*/
public class RandomAccessMode
{
-/**
- * read
- */
-public static final RandomAccessMode READ = new RandomAccessMode(true,
false);
-
-/**
- * read/write
- */
-public static final RandomAccessMode READWRITE = new
RandomAccessMode(true, true);
-
-
-private final boolean read;
-private final boolean write;
-
-private RandomAccessMode(final boolean read, final boolean write)
-{
-this.read = read;
-this.write = write;
-}
-
-public boolean requestRead()
-{
-return read;
-}
-
-public boolean requestWrite()
-{
-return write;
-}
+ /**
+* read
+*/
+ public static final RandomAccessMode READ = new RandomAccessMode(true,
false);
+
+ /**
+* read/write
+*/
+ public static final RandomAccessMode READWRITE = new
RandomAccessMode(true, true);
+
+
+ private final boolean read;
+ private final boolean write;
+
+ private RandomAccessMode(final boolean read, final boolean write)
+ {
+ this.read = read;
+ this.write = write;
+ }
+
+ public boolean requestRead()
+ {
+ return read;
+ }
+
+ public boolean requestWrite()
+ {
+ return write;
+ }
+
+ public String getModeString()
+ {
+ if (requestRead())
+ {
+ if (requestWrite())
+ {
+ return rw; // NON-NLS
+ }
+ else
+ {
+ return r; // NON-NLS
+ }
+ }
+ else if (requestWrite())
+ {
+ return w; // NON-NLS
+ }
+
+ return ;
+ }
}
Modified:
jakarta/commons/proper/vfs/trunk/sandbox/src/main/java/org/apache/commons/vfs/provider/smb/SmbFileRandomAccessContent.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/vfs/trunk/sandbox/src/main/java/org/apache/commons/vfs/provider/smb/SmbFileRandomAccessContent.java?view=diffrev=537714r1=537713r2=537714
==
---
jakarta/commons/proper/vfs/trunk/sandbox/src/main/java/org/apache/commons/vfs/provider/smb/SmbFileRandomAccessContent.java
(original)
+++
[jira] Resolved: (VFS-133) Add RandomAccessMode.getModeString()
[ https://issues.apache.org/jira/browse/VFS-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Ivankovits resolved VFS-133. -- Resolution: Fixed Fix Version/s: 1.1 Thanks for the patch Add RandomAccessMode.getModeString() Key: VFS-133 URL: https://issues.apache.org/jira/browse/VFS-133 Project: Commons VFS Issue Type: New Feature Affects Versions: later Reporter: Adam Heath Priority: Trivial Fix For: 1.1 Attachments: feature_RandomAccessMode-getModeString.patch As $summary, that returns r, w, rw, or , as appropriate. -- 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: r537715 - in /jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider: DefaultFileContent.java FileContentThreadData.java
Author: imario
Date: Sun May 13 22:54:12 2007
New Revision: 537715
URL: http://svn.apache.org/viewvc?view=revrev=537715
Log:
VFS-134: fixed memory leaks - Thanks to Adam Heath for the patch
Modified:
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/DefaultFileContent.java
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/FileContentThreadData.java
Modified:
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/DefaultFileContent.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/DefaultFileContent.java?view=diffrev=537715r1=537714r2=537715
==
---
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/DefaultFileContent.java
(original)
+++
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/DefaultFileContent.java
Sun May 13 22:54:12 2007
@@ -571,7 +571,7 @@
}
finally
{
-endRandomAccess(content);
+endRandomAccess(this);
}
}
}
Modified:
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/FileContentThreadData.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/FileContentThreadData.java?view=diffrev=537715r1=537714r2=537715
==
---
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/FileContentThreadData.java
(original)
+++
jakarta/commons/proper/vfs/trunk/core/src/main/java/org/apache/commons/vfs/provider/FileContentThreadData.java
Sun May 13 22:54:12 2007
@@ -19,7 +19,6 @@
import org.apache.commons.vfs.FileSystemException;
import org.apache.commons.vfs.RandomAccessContent;
-import java.io.IOException;
import java.io.InputStream;
import java.util.ArrayList;
@@ -82,7 +81,7 @@
public void removeInstr(InputStream instr)
{
-this.instrs.remove(instr);
+this.rastrs.remove(instr);
}
public Object removeRastr(int pos)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: A problem creating Java VM using JNI_CreateJavaVM
Hi Sagi, sagi nachum wrote on Saturday, May 12, 2007 10:21 AM: [snip] Any one have a solution? I cannot see that your problem has anything to do with any component of Apache Jakarta Commons. Therefore I doubt that you will receive an answer - even if you continue to post this question again - since it is simply off topic. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (VFS-134) Memory leak closing RandomAccessContent.
[ https://issues.apache.org/jira/browse/VFS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Ivankovits resolved VFS-134. -- Resolution: Fixed Fix Version/s: 1.1 Wow - great catch. Thanks alot for the patch! Memory leak closing RandomAccessContent. Key: VFS-134 URL: https://issues.apache.org/jira/browse/VFS-134 Project: Commons VFS Issue Type: Bug Affects Versions: 1.1 Reporter: Adam Heath Fix For: 1.1 Attachments: fix_ThreadData-remove-Random.patch Closing RandomAccessContent causes a memory leak, because the object is removed from the wrong container. -- 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]
