April 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-349) AbstractJcrNode.addNode Does Not Add jcr:uuid Property if Primary Type Extends mix:referenceable

by Brian Carothers (JIRA)

AbstractJcrNode.addNode Does Not Add jcr:uuid Property if Primary Type Extends mix:referenceable ------------------------------------------------------------------------------------------------ Key: DNA-349 URL: https://jira.jboss.org/jira/browse/DNA-349 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.3 Reporter: Brian Carothers Priority: Minor Attachments: DNA-349.patch If a node is loaded from the repository with a primary type that has mix:referenceable as a supertype, the mandatory, protected jcr:uuid property is properly set. If a new node is added with the same primary type, the jcr:uuid property is not set. When the TCK tests are changed to use a default node type which has mix:referenceable as a supertype (which must be done to make the tests in SetValueNodeTest pass), this issue causes NodeAddMixinTest.testAddMixinReferenceable to fail. -- 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-348) AbstractJcrNode.checkin and .checkout Throws the Wrong Exception Type

by Brian Carothers (JIRA)

AbstractJcrNode.checkin and .checkout Throws the Wrong Exception Type --------------------------------------------------------------------- Key: DNA-348 URL: https://jira.jboss.org/jira/browse/DNA-348 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.3 Reporter: Brian Carothers Priority: Minor Section 8.2.14.1 of the 1.0.1 spec says that Node.checkin() and Node.checkout(): "If this node is not versionable, an UnsupportedRepositoryOperationException is thrown." AbstractJcrNode currently throws an UnsupportedOperationException. This causes about 12 tests to fail in the (currently commented out) SerializationTest in the JR TCK tests. -- 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-347) JcrQuery.storeAsNode Is Not Implemented

by Brian Carothers (JIRA)

JcrQuery.storeAsNode Is Not Implemented --------------------------------------- Key: DNA-347 URL: https://jira.jboss.org/jira/browse/DNA-347 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.3 Reporter: Brian Carothers Priority: Minor JcrQuery.storeAsNode currently throws an UnsupportedRepositoryOperationException as per spec for L1-only JCR repositories. Since the intent clearly seems to be that DNA will support L2 functionality (and since the addNode method has been implemented), this would need to change to actually store the query in the given 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
2
0 / 0

[JBoss JIRA] Created: (DNA-346) JR TCK Tests for SetPropertyStringTest and SetPropertyValueTest Fail

by Brian Carothers (JIRA)

JR TCK Tests for SetPropertyStringTest and SetPropertyValueTest Fail -------------------------------------------------------------------- Key: DNA-346 URL: https://jira.jboss.org/jira/browse/DNA-346 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.4 Reporter: Brian Carothers The L2 TCK tests SetPropertyStringTest and SetPropertyValueTest fail. Opening this defect as a placeholder for the patch. -- 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-345) JcrMultiValueProperty.setValues(null) Doesn't Remove Property

by Brian Carothers (JIRA)

JcrMultiValueProperty.setValues(null) Doesn't Remove Property -------------------------------------------------------------- Key: DNA-345 URL: https://jira.jboss.org/jira/browse/DNA-345 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.4 Reporter: Brian Carothers Minor bug that keeps SetValueStringTest in JR TCK from fully passing. -- 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-341) Graph API behavior when removing all property values doesn't reflect that of JCR

by Randall Hauch (JIRA)

Graph API behavior when removing all property values doesn't reflect that of JCR -------------------------------------------------------------------------------- Key: DNA-341 URL: https://jira.jboss.org/jira/browse/DNA-341 Project: DNA Issue Type: Bug Components: API, Graph, JCR Affects Versions: 0.3 Reporter: Randall Hauch Priority: Critical Fix For: 0.4 Section 4.7.3 of the JSR-170 specification (version 1.0.1) states: Every property must have a value. The range of property states does not include having a "null value", or "no value". Setting a property to "null" is equivalent to removing that property. In the case of multi-value properties, the setting of a particular value within the array to null results in the removal of that value and the compacting of the array. As a result it is possible to have a multi- value property with no values (an empty array). See 7.1.5 Adding and Writing Properties. However, currently the Graph API and connector behavior is such that whenever a property is updated (or set) to no values, the property is removed automatically. This means that it is not possible for the Graph API or connectors to support a multi-valued JCR property with no values. -- 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
6
0 / 0

[JBoss JIRA] Created: (DNA-344) JcrSession.getValueFactory.create(String, int) Does Not Fail Fast as per Specification

by Brian Carothers (JIRA)

JcrSession.getValueFactory.create(String, int) Does Not Fail Fast as per Specification -------------------------------------------------------------------------------------- Key: DNA-344 URL: https://jira.jboss.org/jira/browse/DNA-344 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.4 Reporter: Brian Carothers Section 7.1.5.3 of the JCR 1.0.1 specification (pg 199) indicates that ValueFactory.create(String value, int propertyType) should throw a ValueFormatException if value cannot be converted to the correct type. We currently defer all casts of the value and do not fail fast. This prevents one of the test cases in the L2 TCK test ValueFactoryTest from passing successfully. -- 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-342) Wrong Values is Cast When Setting Property with Castable Type

by Brian Carothers (JIRA)

Wrong Values is Cast When Setting Property with Castable Type ------------------------------------------------------------- Key: DNA-342 URL: https://jira.jboss.org/jira/browse/DNA-342 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.4 Reporter: Brian Carothers If one sets a property with a single value that is not the same as the required type of the definition but is castable to the required type of the definition (e.g., setting a binary property with a string value), SessionCache.setProperty tries to convert the JcrValue object (which ends up converting JcrValue.toString) instead of the converting the value that the JcrValue object wraps. -- 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-340) Projection of Node Types onto System View

by Brian Carothers (JIRA)

Projection of Node Types onto System View ----------------------------------------- Key: DNA-340 URL: https://jira.jboss.org/jira/browse/DNA-340 Project: DNA Issue Type: Feature Request Components: JCR Affects Versions: 0.4 Reporter: Brian Carothers Priority: Minor It may be useful if DNA projected its JCR node types onto the system view in a manner analogous to the way that permanent namespace mappings are projected. -- 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
5
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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues April 2009