September 2008 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-224) dna-connector-federation: one test in FederatingCommandExecutorTest doesn't work with JDK 1.6.0_05 on Mac OS X

by Serge Emmanuel Pagop (JIRA)

dna-connector-federation: one test in FederatingCommandExecutorTest doesn't work with JDK 1.6.0_05 on Mac OS X -------------------------------------------------------------------------------------------------------------- Key: DNA-224 URL: https://jira.jboss.org/jira/browse/DNA-224 Project: DNA Issue Type: Bug Components: Connectors Affects Versions: 0.2 Environment: testing Reporter: Serge Emmanuel Pagop Assignee: Randall Hauch Fix For: 0.2 first I change my jdk 1.5 to the jdk version "1.6.0_05" and I tried to run "mvn clean install" and the test process is broken in the dna-connector-federation module with an error (see below), but with the jdk 1.5 there is no problem. ------------------------------------------------------------------------------- Test set: org.jboss.dna.connector.federation.executor.FederatingCommandExecutorTest ------------------------------------------------------------------------------- Tests run: 21, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.105 sec <<< FAILURE! shouldLoadContributionsForRootNodeFromSources(org.jboss.dna.connector.federation.executor.FederatingCommandExecutorTest) Time elapsed: 0.005 sec <<< FAILURE! java.lang.AssertionError: Expected: (a iterator containing <{}a> and a iterator containing <{}b>) got: <org.jboss.dna.connector.federation.contribution.Contribution$TwoValueIterator@1d83004b> at org.junit.Assert.assertThat(Assert.java:502) at org.junit.Assert.assertThat(Assert.java:492) at org.jboss.dna.connector.federation.executor.FederatingCommandExecutorTest.shouldLoadContributionsForRootNodeFromSources(FederatingCommandExecutorTest.java:265) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59) at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98) at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79) at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87) at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77) at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42) at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88) at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51) at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37) at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997) -- 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

15 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (DNA-152) Utilize SequencingContext to use the MIME type

by Randall Hauch (JIRA)

Utilize SequencingContext to use the MIME type ---------------------------------------------- Key: DNA-152 URL: http://jira.jboss.com/jira/browse/DNA-152 Project: DNA Issue Type: Sub-task Components: Sequencers Reporter: Randall Hauch Priority: Critical Fix For: 0.2 This is required before this sequencer can be uses. -- 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

15 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (DNA-90) Implement namespace management

by Randall Hauch (JIRA)

Implement namespace management ------------------------------ Key: DNA-90 URL: http://jira.jboss.com/jira/browse/DNA-90 Project: DNA Issue Type: Sub-task Reporter: Randall Hauch -- 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

15 years, 7 months

2
7
0 / 0

[JBoss JIRA] Updated: (DNA-46) DNA should provide a JCR 1.0 API (JSR-170) implementation

by Johnny Verhaeg (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-46?page=com.atlassian.jira.plugin.... ] Johnny Verhaeg updated DNA-46: ------------------------------ Fix Version/s: 0.3 (was: 0.2) Affects Version/s: 0.2 > DNA should provide a JCR 1.0 API (JSR-170) implementation > --------------------------------------------------------- > > Key: DNA-46 > URL: https://jira.jboss.org/jira/browse/DNA-46 > Project: DNA > Issue Type: Feature Request > Components: API, JCR > Affects Versions: 0.2 > Reporter: Randall Hauch > Assignee: Johnny Verhaeg > Priority: Critical > Fix For: 0.3 > > > DNA should provide a JCR 1.0 API (JSR-170) implementation. -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (DNA-221) Define nodes that represent queries/searches, with children representing the results of the searches

by Randall Hauch (JIRA)

Define nodes that represent queries/searches, with children representing the results of the searches ---------------------------------------------------------------------------------------------------- Key: DNA-221 URL: https://jira.jboss.org/jira/browse/DNA-221 Project: DNA Issue Type: Feature Request Components: Analysis and Reporting Affects Versions: 0.2 Reporter: Randall Hauch DNA should provide a way for a search to be saved as a node and for the results of the search be shown as children of the node. One way is to define a query node (with the query stored on the node), and to find these and interpret these. Another is to create a "search repository source" with a node per query and the location(s) where each query node is to be projected; the source would then be able to return the results of the query as children. This latter approach would be beneficial in that the query could define the results be returned organized into different facets, and these facets be returned as children with the results (or remaining facets) be returned below the facets. (See also DNA-199 for a similar feature based upon data in a SQL database.) -- 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

15 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-220) Path segment without an index is not considered equal to a segment with an index of 1

by Randall Hauch (JIRA)

Path segment without an index is not considered equal to a segment with an index of 1 -------------------------------------------------------------------------------------- Key: DNA-220 URL: https://jira.jboss.org/jira/browse/DNA-220 Project: DNA Issue Type: Bug Components: SPI Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.2 According to JCR, a path without a same-name-sibling index should be treated equivalently to a path where the same-name-sibling indexes are all 1. For example, "/a/b/c" should be equivalent to "/a[1]/b[1]/c[1]". (See section 4.3.1 of the JSR-170 specification for details.) This is not the case with the BasicPathSegment implementation of Path.Segment. -- 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

15 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-178) Complete JCR implementation enough to support simple read-only usage

by Johnny Verhaeg (JIRA)

Complete JCR implementation enough to support simple read-only usage -------------------------------------------------------------------- Key: DNA-178 URL: https://jira.jboss.org/jira/browse/DNA-178 Project: DNA Issue Type: Sub-task Reporter: Johnny Verhaeg Assignee: Johnny Verhaeg -- 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

15 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (DNA-172) Java sequencer code has problem with package annotations

by Randall Hauch (JIRA)

Java sequencer code has problem with package annotations -------------------------------------------------------- Key: DNA-172 URL: http://jira.jboss.com/jira/browse/DNA-172 Project: DNA Issue Type: Bug Components: Sequencers Reporter: Randall Hauch Assigned To: Serge Emmanuel Pagop Fix For: 0.2 The "dna-sequencer-java" project has an "MySource.java" source file in the "src/test/resources/org/acme" that is used in some of the tests. Because the "src/test/resources" folder is considered a source folder (at least within the Eclipse project), the Eclipse compiler is compiling this class and generating this error: MySource.java line 22: Package annotations must be in file package-info.java Maven is okay, probably because the "src/test/resources" folder is not considered source and is not compiled (although the contents are added to the classpath for tests). However, if this code is intended to be a valid and well-formed example, then the package annotation should go into a "package-info.java" file. This is considered a "strongly recommended" best practice by the Java Language Specification (http://java.sun.com/docs/books/jls/third_edition/html/packages.html#7.4.1.1): "The manner in which this restriction is enforced must, of necessity, vary from implementation to implementation. The following scheme is strongly recommended for file-system-based implementations: The sole annotated package declaration, if it exists, is placed in a source file called package-info.java in the directory containing the source files for the package. This file does not contain the source for a class called package-info.java; indeed it would be illegal for it to do so, as package-info is not a legal identifier. Typically package-info.java contains only a package declaration, preceded immediately by the annotations on the package. While the file could technically contain the source code for one or more package-private classes, it would be very bad form. "It is recommended that package-info.java, if it is present, take the place of package.html for javadoc and other similar documentation generation systems. If this file is present, the documentation generation tool should look for the package documentation comment immediately preceding the (possibly annotated) package declaration in package-info.java. In this way, package-info.java becomes the sole repository for package level annotations and documentation. If, in future, it becomes desirable to add any other package-level information, this file should prove a convenient home for this information. " However, it is quite possible that this code is intentionally different from the best practice, in which case the test cases should probably also have other examples of source that is not well-formed and invalid. Consequently, such test source should probably belong in folder that is not considered a source folder by Maven or Eclipse (or any other IDE in use). -- 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

15 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (DNA-100) javadoc for org.jboss.dna.repository.sequencers.SequencerPathExpression should contain full explanation of syntax for path expressions

by Greg Haber (JIRA)

javadoc for org.jboss.dna.repository.sequencers.SequencerPathExpression should contain full explanation of syntax for path expressions -------------------------------------------------------------------------------------------------------------------------------------- Key: DNA-100 URL: http://jira.jboss.com/jira/browse/DNA-100 Project: DNA Issue Type: Bug Components: Documentation Affects Versions: 0.1 Reporter: Greg Haber Priority: Minor The javadoc for org.jboss.dna.repository.sequencer.SequencerPathExpression for version 0.1 (and also the trunk as of build 234) only has a brief example of a valid sequencer path expression. It should be revised to contain a complete description of the syntax for such path expressions. Without such an explanation, user that want more detail than in the 0.1 getting started guide need to study the source for this class and the examples in org.jboss.dna.repository.sequencer.SequencerPathExpressionTest to determine syntax, which (for me at least) is non-trivial. Once such an explanation is in place, the "for a more detailed explanation" text on the sequencing_service.html can link right to the javadoc. -- 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

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (DNA-69) Note in section 1 of Using JBoss DNA should explain use of criteria for image sequencer config path expression

by Johnny Verhaeg (JIRA)

Note in section 1 of Using JBoss DNA should explain use of criteria for image sequencer config path expression -------------------------------------------------------------------------------------------------------------- Key: DNA-69 URL: http://jira.jboss.com/jira/browse/DNA-69 Project: DNA Issue Type: Bug Components: Documentation Affects Versions: 0.1 Reporter: Johnny Verhaeg Priority: Minor All parts of the path //(*.(jpg|jpeg|gif|bmp|pcx|png))[*]/jcr:content[@jcr:data] => /images/$1 are explained, except for the 2 criteria in square brackets. -- 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

15 years, 8 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues September 2008