August 2008 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-197) BasicPath.getAncestor() should return null for root path

by Johnny Verhaeg (JIRA)

BasicPath.getAncestor() should return null for root path -------------------------------------------------------- Key: DNA-197 URL: https://jira.jboss.org/jira/browse/DNA-197 Project: DNA Issue Type: Bug Reporter: Johnny Verhaeg This method currently returns the root path itself in an attempt to make method chaining more consistent, but this makes the semantics of getAncestor() incorrect for the root path and the behavior inconsistent with the corresponding isAncestorOf() method, which returns false for rootPath.isAncestorOf(rootPath). getAncestor(int depth) will need to be changed accordingly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (DNA-96) ValueFormatException should be replaced by existing JDK IllegalArgumentException and UnsupportedOperationException in ValueFactories

by Johnny Verhaeg (JIRA)

ValueFormatException should be replaced by existing JDK IllegalArgumentException and UnsupportedOperationException in ValueFactories ------------------------------------------------------------------------------------------------------------------------------------ Key: DNA-96 URL: http://jira.jboss.com/jira/browse/DNA-96 Project: DNA Issue Type: Feature Request Components: SPI Affects Versions: 0.1 Reporter: Johnny Verhaeg Fix For: 0.2 1) There may be a development situation where it is advantageous to know a passed-in path, segment, etc., is invalid (e.g., due to bad index value, character used, etc.) vs. a bad usage of the factory, such as trying to convert a Boolean value into a Date. 2) Non-ValueFactories classes that interact with the ValueFactories, such as BasicName, will need to throw IllegalArgumentException anyway when an invalid name is passed in, meaning the ValueFactories that interact with it would need to catch the IAE and re-throw as a ValueFormatException. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (DNA-207) I18n classes should not require methods related to locales and problems

by Johnny Verhaeg (JIRA)

I18n classes should not require methods related to locales and problems ----------------------------------------------------------------------- Key: DNA-207 URL: https://jira.jboss.org/jira/browse/DNA-207 Project: DNA Issue Type: Feature Request Components: Common Affects Versions: 0.1 Reporter: Johnny Verhaeg Assignee: Johnny Verhaeg Priority: Minor Fix For: 0.2 Previously we decided to require all I18n classes to have the following methods: public static Set<Locale> getLocalizationProblemLocales() { return I18n.getLocalizationProblemLocales(JcrI18n.class); } public static Set<String> getLocalizationProblems() { return I18n.getLocalizationProblems(JcrI18n.class); } public static Set<String> getLocalizationProblems( Locale locale ) { return I18n.getLocalizationProblems(JcrI18n.class, locale); } Since these are merely for convenience, we've backed off of requiring these. The only change is the AbstractI18nTest class should be changed to use the corresponding methods in I18n.class rather than depending upon each internationalization class defining them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-206) AbstractI18nTest no longer catches problems after last changes to I18n

by Johnny Verhaeg (JIRA)

AbstractI18nTest no longer catches problems after last changes to I18n ---------------------------------------------------------------------- Key: DNA-206 URL: https://jira.jboss.org/jira/browse/DNA-206 Project: DNA Issue Type: Bug Components: Testing Affects Versions: 0.1 Reporter: Johnny Verhaeg Assignee: Johnny Verhaeg Priority: Minor Fix For: 0.2 After I18n was changed to separate its initialize method into two components, initialize(), which is done at construction, and localize(), which is done lazily upon usage of I18n fields, the test no longer catches problems. This is because of the lazy localization. Test needs to be changed to always perform the check of global problems after localization has been triggered by analyzing the fields. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-204) Unit tests for dna-example-sequencers are not being executed in the Maven builds in the nightly Hudson jobs

by Randall Hauch (JIRA)

Unit tests for dna-example-sequencers are not being executed in the Maven builds in the nightly Hudson jobs ----------------------------------------------------------------------------------------------------------- Key: DNA-204 URL: https://jira.jboss.org/jira/browse/DNA-204 Project: DNA Issue Type: Bug Components: Development Environment Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.2 See DNA-203; apparently these tests are not being included in the continuous or nightly Hudson builds. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-203) Unit tests for dna-example-sequencers don't work

by Randall Hauch (JIRA)

Unit tests for dna-example-sequencers don't work ------------------------------------------------ Key: DNA-203 URL: https://jira.jboss.org/jira/browse/DNA-203 Project: DNA Issue Type: Bug Components: Sequencers Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.2 Serge reported the following: Today, I took a look at the dna-example-sequencers and ran the "SequencingClientTest" test. But unfortunately shouldUploadAndSequencePngFile, shouldUploadAndSequenceJpegFile, shouldUploadAndSequencePictFile all fail with this exception: 11:51:03,806 ERROR Error in repository while sequencer Image Sequencer is sequencing node repo/default=>/a/b/caution.png/jcr:content javax.jcr.nodetype.ConstraintViolationException: cannot set the value of a protected property /images/caution.png/image:metadata/jcr:primaryType at org.apache.jackrabbit.core.PropertyImpl.checkSetValue(PropertyImpl.java:224) at org.apache.jackrabbit.core.PropertyImpl.setValue(PropertyImpl.java:775) at org.apache.jackrabbit.core.NodeImpl.setProperty(NodeImpl.java:2211) at org.jboss.dna.repository.sequencers.StreamSequencerAdapter.saveOutput(StreamSequencerAdapter.java:230) at org.jboss.dna.repository.sequencers.StreamSequencerAdapter.execute(StreamSequencerAdapter.java:154) at org.jboss.dna.repository.sequencers.SequencingService.processChangedNode(SequencingService.java:576) at org.jboss.dna.repository.sequencers.SequencingService$1.run(SequencingService.java:484) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:613) 11:51:04,988 ERROR Error in repository while sequencer Image Sequencer is sequencing node repo/default=>/a/b/caution.jpeg/jcr:content javax.jcr.nodetype.ConstraintViolationException: cannot set the value of a protected property /images/caution.jpeg/image:metadata/jcr:primaryType at org.apache.jackrabbit.core.PropertyImpl.checkSetValue(PropertyImpl.java:224) at org.apache.jackrabbit.core.PropertyImpl.setValue(PropertyImpl.java:775) at org.apache.jackrabbit.core.NodeImpl.setProperty(NodeImpl.java:2211) at org.jboss.dna.repository.sequencers.StreamSequencerAdapter.saveOutput(StreamSequencerAdapter.java:230) at org.jboss.dna.repository.sequencers.StreamSequencerAdapter.execute(StreamSequencerAdapter.java:154) at org.jboss.dna.repository.sequencers.SequencingService.processChangedNode(SequencingService.java:576) at org.jboss.dna.repository.sequencers.SequencingService$1.run(SequencingService.java:484) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:613) 11:51:07,693 ERROR Error in repository while sequencer Mp3 Sequencer is sequencing node repo/default=>/a/b/test.mp3/jcr:content javax.jcr.nodetype.ConstraintViolationException: cannot set the value of a protected property /mp3s/test.mp3/mp3:metadata/jcr:primaryType at org.apache.jackrabbit.core.PropertyImpl.checkSetValue(PropertyImpl.java:224) at org.apache.jackrabbit.core.PropertyImpl.setValue(PropertyImpl.java:775) at org.apache.jackrabbit.core.NodeImpl.setProperty(NodeImpl.java:2211) at org.jboss.dna.repository.sequencers.StreamSequencerAdapter.saveOutput(StreamSequencerAdapter.java:230) at org.jboss.dna.repository.sequencers.StreamSequencerAdapter.execute(StreamSequencerAdapter.java:154) at org.jboss.dna.repository.sequencers.SequencingService.processChangedNode(SequencingService.java:576) at org.jboss.dna.repository.sequencers.SequencingService$1.run(SequencingService.java:484) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:613) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-202) DateTime interface in SPI should have methods that return offsets into the future or past

by Randall Hauch (JIRA)

DateTime interface in SPI should have methods that return offsets into the future or past ----------------------------------------------------------------------------------------- Key: DNA-202 URL: https://jira.jboss.org/jira/browse/DNA-202 Project: DNA Issue Type: Feature Request Components: SPI Reporter: Randall Hauch Assignee: Randall Hauch Priority: Minor Fix For: 0.2 Add to the DateTime interface (and implementations) methods to return other DateTime instants that are offset into the future or past (e.g., "plus" and "minus"). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-198) JackrabbitDerbyStressTest throws exceptions intermittently without failing

by Johnny Verhaeg (JIRA)

JackrabbitDerbyStressTest throws exceptions intermittently without failing -------------------------------------------------------------------------- Key: DNA-198 URL: https://jira.jboss.org/jira/browse/DNA-198 Project: DNA Issue Type: Bug Components: Testing Affects Versions: 0.1 Reporter: Johnny Verhaeg Fix For: 0.2 Attachments: JackRabbitDerbyStressTestFailure.txt Attached file contains a sample of output. The errors in this case begin with the 1000 node test, but I've seen that particular test work sometimes without the error (when run along with the rest of the test class). If each test method is run separately, each test seems to pretty consistently run without error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (DNA-200) Sequence JBoss license files

by Randall Hauch (JIRA)

Sequence JBoss license files ---------------------------- Key: DNA-200 URL: https://jira.jboss.org/jira/browse/DNA-200 Project: DNA Issue Type: Feature Request Components: Sequencers Reporter: Randall Hauch Priority: Minor Fix For: Future Releases Create a sequencer that is able to process license files for the JBoss products and that can extract the useful information contained in each. This would facilitate a repository that is used for license management (along with information about a customer's subscriptions; what they bought). This may be useful for RHQ/Spacewalk. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-199) Federate content from relational databases

by Randall Hauch (JIRA)

Federate content from relational databases ------------------------------------------ Key: DNA-199 URL: https://jira.jboss.org/jira/browse/DNA-199 Project: DNA Issue Type: Feature Request Components: Connectors Reporter: Randall Hauch Fix For: Future Releases Create a connector for the federation engine that contributes and exposes the content of a query against a relational database. One option is to simply place all records below a single node, but a more useful approach would be to have the query use GROUP BY and to then create a level in the content hierarchy that represents each group clause and ranges or actual values. For example, consider a query that selects products and then groups by product type, by price, and then by name. This would correspond to a repository structure with one level for the product type (values for the node names at this level might be "Exterior", "Interior", "Automotive", etc.), a second level for price (e.g., "Under $10", "$10-$20", etc.), and a third level for the models (e.g., "ACME SuperPaint", "5-gallon Gas Tank", etc.). The lowest level in the hierarchy may need to be the primary key (in other words, the GROUP BY clauses create categories under which the individual records appear). This same approach would allow a table's contents to be organized by it's compound (primary) key simply by creating a query that uses GROUP BY for each of the columns in the compound key. Note that this is not the same as a connector that provides access to a relational database schema (see DNA-37). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues August 2008