Re: commons digester DTD
On Sat, 2008-03-29 at 23:59 -0400, Rahul Akolkar wrote: > On 3/29/08, Jianguo Zhang <[EMAIL PROTECTED]> wrote: > > it seems commons digester DTD have no attributes definition for > > node-create-rule. while it defines object-param-rule two times. Is the > > second one of object-param-rule should be node-create-rule. > > > > > Seems likely, please open an issue in JIRA [1], if one isn't there > already for this. > > Posts on the list run the risk of getting lost unless acted upon > immediately, JIRA will keep it on the radar. I've created a JIRA issue for this: http://issues.apache.org/jira/browse/DIGESTER-123
[jira] Commented: (CONFIGURATION-319) Reload(addConfigurationListern) not works for CompositeConfiguration
[ https://issues.apache.org/jira/browse/CONFIGURATION-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583826#action_12583826 ] Oliver Heger commented on CONFIGURATION-319: You are right, CompositeConfiguration does not correctly handle change listeners and change events. Could you try CombinedConfiguration instead? This class should provide the functionality you need, and it also has some other advantages over CompositeConfiguration - especially it is a truly hierarchical configuration. CompositeConfiguration is a bit, well, old-fashioned. In the long run it should be replaced by CombinedConfiguration. So I wonder if it makes sense to address this issue when there is a working alternative. > Reload(addConfigurationListern) not works for CompositeConfiguration > > > Key: CONFIGURATION-319 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-319 > Project: Commons Configuration > Issue Type: Bug >Affects Versions: 1.5 > Environment: Linux 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:54:53 EST > 2006 i686 i686 i386 GNU/Linux >Reporter: Sandeep Kumar > > I created 2 XMLConfiguration and added this to CompositeConfiguration using > addConfiguration. Now I addConfigurationListern at CompositeConfiguration > level. Currently CompositeConfiguration.addConfigurationListern is not > overriden and addConfigurationListern never get registeded to any of actual > configuration. The solution could be override the > CompositeConfiguration.addConfigurationListern which iterate though > configList(a private member of CompositeConfiguration class) and registed > listern to all the configuration. In current code this is broken funtionality > and callback ConfigurationListener.configurationChanged never fired. > while reproducing this problem I am calling > CompositeConfiguration.getProperty() every minute for reloading from another > thread. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DIGESTER-123) xmlrules dtd does not define xmlattrs for node-create-rule
xmlrules dtd does not define xmlattrs for node-create-rule -- Key: DIGESTER-123 URL: https://issues.apache.org/jira/browse/DIGESTER-123 Project: Commons Digester Issue Type: Bug Affects Versions: 1.8 Reporter: Simon Kitching As reported by Jianguo Zhang, the file digester-rules.dtd has what appears to be a copy-and-paste error, defining the xml attrs for object-param-rule a second time, when it should be defining xml attrs for node-create-rule. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COLLECTIONS-213) CollectionUtils API extension: algorithm methods accept an Iterator argument
[ https://issues.apache.org/jira/browse/COLLECTIONS-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583809#action_12583809 ] Ryan Ovrevik commented on COLLECTIONS-213: -- Sorry for the delay in responding to the suggestion to close this feature request. Unless I am missing something, the functionality provided by creating an intermediate list is not sufficient for our use cases. We use iterators in a pipes and filters-based batch process. The iterators are backed by fifo queues that are populated from database records. Using the intermediate list approach would require that all items piped through the process would first be read into (and stay in) memory. > CollectionUtils API extension: algorithm methods accept an Iterator argument > > > Key: COLLECTIONS-213 > URL: https://issues.apache.org/jira/browse/COLLECTIONS-213 > Project: Commons Collections > Issue Type: Improvement > Components: Core >Reporter: Dusan Chromy > Fix For: 3.3 > > Attachments: CollectionUtils.java, TestCollectionUtils.java > > > I just finished the Iterator additions to CollectionUtils, including test > cases and I am going to > attach them to this issue very shortly (basically as soon as I figure out how > attaching in JIRA works :) > At first I was thinking for a while whether CollectionUtils is a good place > to accomodate the methods with the > new signature, until I noticed the collect method already accepts an Iterator > argument. > Following methods now accept an Iterator argument (besides collect): > cardinality > find > forAllDo > countMatches > exists > I also noticed cardinality used to throw a NPE if the collection argument was > null. > I see no reason why it should not return zero. The Iterator flavour does > return zero > and I also modified the Collection version to return zero (including Javadoc > modification) for the sake of consistence. > I stopped to think for a while before touching the method, but the fact > that the Javadoc does not mention "may not be null" made me think the NPE is > not thrown > intentionally. And after all, cardinality(..) is nothing else than > specialized countMatches(..), > which returns 0 for null collection. However, feel free to reject the change > to the cardinality(Object,Collection) > method if you think otherwise. > I worked on a fresh checkout from subversion and I just updated few minutes > ago to make sure I have modified > the latest version. Anyway, please double-check before commiting the changes. > Cheers, > Dusan > > I think that these methods would make useful additions to the API. > > > > I don't have the time to do much collections work these days, but if you > > want to code the methods with test cases and attach them to JIRA then that > > would be great. > > > > Stephen > > > > > > [EMAIL PROTECTED] wrote: > > > > > I've been using some algorithm methods from the CollectionUtils, for > > > example > > > find(Collection, Predicate) > > > exists(Collection, Predicate) > > > countMatches(Collection, Predicate) > > > forAllDo(Collection, Closure) > > > > > > However, I would also like to be able to use these algorithms with an > > > Iterator: > > > > > > find(Iterator, Predicate) > > > exists(Iterator, Predicate) > > > countMatches(Iterator, Predicate) > > > forAllDo(Iterator, Closure) > > > > > > The obvious workaround is to use IteratorUtils.toList(Iterator), however > > > this comes at the cost of constructing a list object (an ArrayList > > > presumably) which could be avoided, as the Iterator itself is sufficient > > > for the above algorithms to work. > > > > > > What do you think? Is there any reason not to provide the algorithms for > > > an Iterator? I personally think that the algorithms should have been > > > there for Iterators in the first place, because every collection is > > > Iterable (or has an Iterator, prior to JDK 5.0). > > > > > > If noone is interested or has time to implement these changes, I can also > > > contribute to the project - but at the moment I just wanted to discuss > > > the idea / check if this has been already considered or planned. > > > > > > Best Regards, > > > > > > Dusan Chromy > > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CONFIGURATION-314) Allow custom separator characters when writing out PropertiesConfiguration
[ https://issues.apache.org/jira/browse/CONFIGURATION-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583806#action_12583806 ] David Felsenthal commented on CONFIGURATION-314: As well as a custom separator on write, a custom separator on read is needed. I have to deal with legacy non-standard ini files , with # in the text fields, not quoted or escaped. I would have preferred to be able to override and extend INIConfiguration, but could not. Instead, I too, had to copy and modify chunks of code. > Allow custom separator characters when writing out PropertiesConfiguration > -- > > Key: CONFIGURATION-314 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-314 > Project: Commons Configuration > Issue Type: Improvement >Affects Versions: 1.5 >Reporter: Kenny MacLeod > Fix For: 1.6 > > > While PropertiesConfiguration is tolerant of several different key/value > separator characters when reading a properties stream, it is hard-wired to > use an "=" character when writing them out again. > Can we please have a way to customise this? Seems like a perfect use for the > PropertiesConfigurationLayout. > Sadly, because of the way that PropertiesWriter has been implemented, it's > impossible to extend and override this behaviour without copying large chunks > of code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SANDBOX-223) Update Wiki to reflect information about Validator2
[ https://issues.apache.org/jira/browse/SANDBOX-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583780#action_12583780 ] Rahul Akolkar commented on SANDBOX-223: --- Please try in the correct wiki space ( wiki.a.o/commons rather than wiki.a.o/jakarta-commons ). You should be able to add pages. > Update Wiki to reflect information about Validator2 > --- > > Key: SANDBOX-223 > URL: https://issues.apache.org/jira/browse/SANDBOX-223 > Project: Commons Sandbox > Issue Type: Task > Components: Validator2 > Environment: All >Reporter: Mohammad Nour >Priority: Minor > > Update Wiki to reflect information about Validator2: > --- > 1- General info. > 2- Project info. > 2.1 SVN location. > 3- User guide. > 4- Developer guide. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SANDBOX-222) Validator2 design on Wiki
[ https://issues.apache.org/jira/browse/SANDBOX-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583779#action_12583779 ] Rahul Akolkar commented on SANDBOX-222: --- Its moved to: http://wiki.apache.org/commons/Validator Links on main wiki page(s) that still point to jakarta-commons space need updating. > Validator2 design on Wiki > - > > Key: SANDBOX-222 > URL: https://issues.apache.org/jira/browse/SANDBOX-222 > Project: Commons Sandbox > Issue Type: Task > Components: Validator2 > Environment: All >Reporter: Mohammad Nour > > Lay down the design of Validator2 and document it on Wiki - > http://wiki.apache.org/jakarta-commons/Validator . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CONFIGURATION-319) Reload(addConfigurationListern) not works for CompositeConfiguration
Reload(addConfigurationListern) not works for CompositeConfiguration Key: CONFIGURATION-319 URL: https://issues.apache.org/jira/browse/CONFIGURATION-319 Project: Commons Configuration Issue Type: Bug Affects Versions: 1.5 Environment: Linux 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:54:53 EST 2006 i686 i686 i386 GNU/Linux Reporter: Sandeep Kumar I created 2 XMLConfiguration and added this to CompositeConfiguration using addConfiguration. Now I addConfigurationListern at CompositeConfiguration level. Currently CompositeConfiguration.addConfigurationListern is not overriden and addConfigurationListern never get registeded to any of actual configuration. The solution could be override the CompositeConfiguration.addConfigurationListern which iterate though configList(a private member of CompositeConfiguration class) and registed listern to all the configuration. In current code this is broken funtionality and callback ConfigurationListener.configurationChanged never fired. while reproducing this problem I am calling CompositeConfiguration.getProperty() every minute for reloading from another thread. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SANDBOX-223) Update Wiki to reflect information about Validator2
[ https://issues.apache.org/jira/browse/SANDBOX-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583776#action_12583776 ] Mohammad Nour commented on SANDBOX-223: --- As I don't have the permission to add new pages to the Wiki, I will point link in Validator main Wiki page to pages located on my Aapache home page - http://people.apache.org/~mnour/validator2 . > Update Wiki to reflect information about Validator2 > --- > > Key: SANDBOX-223 > URL: https://issues.apache.org/jira/browse/SANDBOX-223 > Project: Commons Sandbox > Issue Type: Task > Components: Validator2 > Environment: All >Reporter: Mohammad Nour >Priority: Minor > > Update Wiki to reflect information about Validator2: > --- > 1- General info. > 2- Project info. > 2.1 SVN location. > 3- User guide. > 4- Developer guide. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SANDBOX-223) Update Wiki to reflect information about Validator2
Update Wiki to reflect information about Validator2 --- Key: SANDBOX-223 URL: https://issues.apache.org/jira/browse/SANDBOX-223 Project: Commons Sandbox Issue Type: Task Components: Validator2 Environment: All Reporter: Mohammad Nour Priority: Minor Update Wiki to reflect information about Validator2: --- 1- General info. 2- Project info. 2.1 SVN location. 3- User guide. 4- Developer guide. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SANDBOX-222) Validator2 design on Wiki
Validator2 design on Wiki - Key: SANDBOX-222 URL: https://issues.apache.org/jira/browse/SANDBOX-222 Project: Commons Sandbox Issue Type: Task Components: Validator2 Environment: All Reporter: Mohammad Nour Lay down the design of Validator2 and document it on Wiki - http://wiki.apache.org/jakarta-commons/Validator . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SANDBOX-221) Reading JSR#303 - Bean Validation
Reading JSR#303 - Bean Validation - Key: SANDBOX-221 URL: https://issues.apache.org/jira/browse/SANDBOX-221 Project: Commons Sandbox Issue Type: Task Components: Validator2 Environment: All Reporter: Mohammad Nour Read JSR#303: - 1- Write down comments if any and send to JSR comments list. 2- Lay down the design of Validator2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DAEMON-109) Adding JvmOptions prevents application from starting
Adding JvmOptions prevents application from starting Key: DAEMON-109 URL: https://issues.apache.org/jira/browse/DAEMON-109 Project: Commons Daemon Issue Type: Bug Environment: All Windows C:\Data\Tomcat\bin>java -version java version "1.6.0_03" Java(TM) SE Runtime Environment (build 1.6.0_03-b05) Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode, sharing) Reporter: David Newcomb Had previously reported this on the Tomcat site, but they say the problem is in your domain https://issues.apache.org/bugzilla/show_bug.cgi?id=44506 Using JvmOptions prevents Tomcat from starting. I have tried: tomcat6.exe --JvmOptions -Xdebug;-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044 tomcat6.exe --JvmOptions -Xdebug#-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044 tomcat6.exe --JvmOptions "-Xdebug#-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044" tomcat6.exe --JvmOptions "-Xdebug#-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044" tomcat6.exe --JvmOptions '-Xdebug#-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044' tomcat6.exe --JvmOptions '-Xdebug;-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044' and the same with ++JvmOptions. On each occasion it reports: [2008-02-28 16:42:19] [420 prunsrv.c] [error] The operation completed successfully. [2008-02-28 16:42:19] [1327 prunsrv.c] [error] Load configuration failed and the log file is not created. C:\Data\Tomcat\bin>java -version java version "1.6.0_03" Java(TM) SE Runtime Environment (build 1.6.0_03-b05) Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode, sharing) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRANSACTION-13) JTA Compliant
[ https://issues.apache.org/jira/browse/TRANSACTION-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583581#action_12583581 ] Jorg Heymans commented on TRANSACTION-13: - It is not possible to vote on resolved issues, please leave the ticket open so people can vote on it. > JTA Compliant > - > > Key: TRANSACTION-13 > URL: https://issues.apache.org/jira/browse/TRANSACTION-13 > Project: Commons Transaction > Issue Type: New Feature >Reporter: Cyrille >Assignee: Jörg Heinicke > Fix For: 2.0 > > > Is there a plan to make Commons-Transaction compliant with JTA (Java > Transaction API) ? > It would be great to get it. > For exemple, in case of a web file upload, we could make one transaction for > tose 2 operations : > 1) writing metadata in database (title,description...), > 2) writing the file on the filesystem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
