August 2008 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-213) Review the graph SPI commands to better handle node identification (e.g., when getting children)

by Randall Hauch (JIRA)

Review the graph SPI commands to better handle node identification (e.g., when getting children) ------------------------------------------------------------------------------------------------ Key: DNA-213 URL: https://jira.jboss.org/jira/browse/DNA-213 Project: DNA Issue Type: Task Components: SPI Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.2 The graph commands in the SPI were an initial attempt to identify the set of functionality that the connectors should support. One problem with the current design is that it's not really feasible or possible to track with each child the identification properties for the child. For example, when getting the children of a node, it's not mandatory (nor that clear) that identification properties be recorded for each child as well. It's very important to provide a way for all nodes (including children) to be fully identified. -- 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

1
6
0 / 0

[JBoss JIRA] Created: (DNA-71) Document development tools and environment

by Randall Hauch (JIRA)

Document development tools and environment ------------------------------------------ Key: DNA-71 URL: http://jira.jboss.com/jira/browse/DNA-71 Project: DNA Issue Type: Task Components: Documentation Affects Versions: 0.1 Reporter: Randall Hauch Fix For: 0.2 We need to document how to set up the Maven Integration for Eclipse plugin. Apparently there's a newer version which defaults to generating the targets in a separate location (e.g., "targetEclipse"). We need to document this, emphasizing that having the Maven Eclipse plugin needs to work the same way that the command line does. -- 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, 1 month

1
9
0 / 0

[JBoss JIRA] Created: (DNA-103) Sequence Excel files

by Randall Hauch (JIRA)

Sequence Excel files -------------------- Key: DNA-103 URL: http://jira.jboss.com/jira/browse/DNA-103 Project: DNA Issue Type: Feature Request Components: Sequencers Reporter: Randall Hauch Fix For: Future Releases Create a sequencer that extracts the content from Excel spreadsheets. Consider using Apache POI (http://poi.apache.org/index.html) to access the Excel files. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (DNA-205) Rename "org.jboss.dna.common.util.ArgCheck" to "org.jboss.dna.common.util.CheckArg"

by Randall Hauch (JIRA)

Rename "org.jboss.dna.common.util.ArgCheck" to "org.jboss.dna.common.util.CheckArg" ----------------------------------------------------------------------------------- Key: DNA-205 URL: https://jira.jboss.org/jira/browse/DNA-205 Project: DNA Issue Type: Task Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Minor Fix For: 0.3 Minor nit, but "CheckArg.isNotNull(...)" is more readable than "ArgCheck.isNotNull(...)". We should do this first thing after the 0.2 release, since it will impact a huge percentage of the code. -- 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, 1 month

1
7
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

17 years, 1 month

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

17 years, 1 month

2
7
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

17 years, 1 month

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

17 years, 1 month

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

17 years, 1 month

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

17 years, 1 month

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues August 2008