March 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-143) Create tests for child node definition counts and quoted strings in the grammar unit tests

by Dan Florian (JIRA)

Create tests for child node definition counts and quoted strings in the grammar unit tests ------------------------------------------------------------------------------------------ Key: DNA-143 URL: http://jira.jboss.com/jira/browse/DNA-143 Project: DNA Issue Type: Sub-task Reporter: Dan Florian -- 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

2
4
0 / 0

[JBoss JIRA] Created: (DNA-264) Connectors may need to determine the MIME type for content

by Randall Hauch (JIRA)

Connectors may need to determine the MIME type for content ---------------------------------------------------------- Key: DNA-264 URL: https://jira.jboss.org/jira/browse/DNA-264 Project: DNA Issue Type: Task Reporter: Randall Hauch Assignee: Randall Hauch Some connectors may need to be able to determine the MIME type for content, and there's currently no way in the connector API to do that. The 'dna-graph' project does have MimeTypeDetector interface, but that's meant as a lower-level interface for an implementation. MimeType was designed to be the main entry point for general components, but that's currently in 'dna-repository' (and connectors don't currently require that). -- 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

1
2
0 / 0

[JBoss JIRA] Created: (DNA-339) JCR Type Registration and Unregistration

by Brian Carothers (JIRA)

JCR Type Registration and Unregistration ---------------------------------------- Key: DNA-339 URL: https://jira.jboss.org/jira/browse/DNA-339 Project: DNA Issue Type: Feature Request Components: JCR Affects Versions: 0.4 Reporter: Brian Carothers It would be useful for DNA to support type registration and unregistration (a la JSR 2.0 (draft) spec section 6.10). -- 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

2
10
0 / 0

[JBoss JIRA] Created: (DNA-338) Definitions That Allow SNS Are Not Used For Nodes Without SNS

by Brian Carothers (JIRA)

Definitions That Allow SNS Are Not Used For Nodes Without SNS ------------------------------------------------------------- Key: DNA-338 URL: https://jira.jboss.org/jira/browse/DNA-338 Project: DNA Issue Type: Bug Components: Graph Affects Versions: 0.4 Reporter: Brian Carothers Currently, RepositoryNodeTypeManager.findChildNodeDefinition will not consider definitions that allow SNS if the child node does not require SNS. That is, if a new child node is added (and, hence, does not yet have any SNS) to a parent node that would only allow the child node with SNS (i.e., there's not definition that supports the child without SNS), findChildNodeDefinition returns null. Section 6.7.7 (regarding child node definitions) in the JCR 1.0 spec reads (in part) that the child node definition indicates "[w]hether this child node can have same-name siblings, meaning that the parent node can have more than one child node of this name." I may be reading too much into the use of the word "can" instead of "must", but I think that SNS definitions allow for a single node, just like multi-valued property definitions support a multi-valued property that happens to have one value. -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (DNA-337) Namespace Registries Create Two Nodes at /jcr:system/dna:namespaces

by Brian Carothers (JIRA)

Namespace Registries Create Two Nodes at /jcr:system/dna:namespaces ------------------------------------------------------------------- Key: DNA-337 URL: https://jira.jboss.org/jira/browse/DNA-337 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.4 Reporter: Brian Carothers Priority: Minor After initializing a repository and creating a session, the system creates two nodes (same name siblings) at /jcr:system/dna:namespaces. This confounds the RepositoryNodeTypeManagers attempts to assign a primary type to either dna:namespaces node as the definition of the dna:system type (the primary type for /jcr:system) does not allow SNS for the dna:namespaces node. -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (DNA-336) JcrValue.asType(int desiredPropertyType) skips a number of valid conversions and has duplicate logic

by Randall Hauch (JIRA)

JcrValue.asType(int desiredPropertyType) skips a number of valid conversions and has duplicate logic ---------------------------------------------------------------------------------------------------- Key: DNA-336 URL: https://jira.jboss.org/jira/browse/DNA-336 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.4 Currently the JcrValue implementation has a method "asType(int propertyType)" that creates a new JcrValue object with the original values converted to the specified type. There are a couple of cases that are missed: 1) The code does not do any conversion to LONG of DOUBLE. However, according to the JCR 1.0 specification, it is possible to convert these if the current type is a STRING, BINARY, DATE, DOUBLE, or LONG. 2) The code does not do any conversion to REFERENCE. However, according to the JCR 1.0 specification, it is possible to convert these if the current type is a STRING, NAME, or BINARY. 3) The conversion to a number of types exclude going to BINARY 4) The conversion to NAME and PATH both have somewhat complex logic to determine if a conversion is possible, even the current value factories do the same checks. The code should just let the value factories do the checks. -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (DNA-306) Add ability to run all TCK unit tests within Hudson, showing success and failure rate

by Randall Hauch (JIRA)

Add ability to run all TCK unit tests within Hudson, showing success and failure rate ------------------------------------------------------------------------------------- Key: DNA-306 URL: https://jira.jboss.org/jira/browse/DNA-306 Project: DNA Issue Type: Task Components: Development Environment, Testing Affects Versions: 0.3 Reporter: Randall Hauch Priority: Minor Fix For: 0.4 Currently our use of the JCR TCK unit tests (again, not the official TCK but a subset of what's run within the TCK) is handled within a JUnit test suite in the "dna-jcr" project, and as we develop new features we're uncommenting tests as we pass them. This does not give us any information about how we're progressing. We want to run the tests (perhaps nightly) and make these stats available to let people know how we're doing and proceeding towards Level 1 and Level 2 compatibility. Comments, thoughts, and approaches welcome. -- 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, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (DNA-305) JcrNodeType.canSetProperty Does Not Enforce Constraints

by Brian Carothers (JIRA)

JcrNodeType.canSetProperty Does Not Enforce Constraints ------------------------------------------------------- Key: DNA-305 URL: https://jira.jboss.org/jira/browse/DNA-305 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.4 Reporter: Brian Carothers JCRNodeType.canSetProperty does not currently perform any validations against the constraints for the property. This does not meet the JCR 1.0 specification and will probably cause L2 tests to fail in the TCK. -- 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, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (DNA-333) BasicName.getString Doesn't Use Provided TextEncoder When the Name Has No Namespace

by Brian Carothers (JIRA)

BasicName.getString Doesn't Use Provided TextEncoder When the Name Has No Namespace ------------------------------------------------------------------------------------ Key: DNA-333 URL: https://jira.jboss.org/jira/browse/DNA-333 Project: DNA Issue Type: Bug Components: Graph Affects Versions: 0.4 Reporter: Brian Carothers If one creates a BasicName with no namespace (e.g., "*") and calls one of the overloaded versions of getString that allows a TextEncoder to be specified, the encoder is not used. -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (DNA-334) Should not allow creating a Name from a string with multiple non-escaped colons

by Randall Hauch (JIRA)

Should not allow creating a Name from a string with multiple non-escaped colons ------------------------------------------------------------------------------- Key: DNA-334 URL: https://jira.jboss.org/jira/browse/DNA-334 Project: DNA Issue Type: Bug Components: Graph Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.4 According to the JCR TCK, it should not be possible to convert the string "a:b:c" into a name, since the second colon is not escaped. -- 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, 1 month

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues March 2009