April 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-357) Hide dna:nodeDefinition Property from Users

by Brian Carothers (JIRA)

Hide dna:nodeDefinition Property from Users ------------------------------------------- Key: DNA-357 URL: https://jira.jboss.org/jira/browse/DNA-357 Project: DNA Issue Type: Feature Request Components: JCR Reporter: Brian Carothers Priority: Minor dna:nodeDefinition is a bit of an odd duck. It is set on every property but doesn't always have a valid JCR definition. This breaks an export-import round trip as the property cannot be set during import. It also breaks a few TCK tests that assume a jcr:xmltext node only has two properties (jcr:primaryType and jcr:xmlcharacters), but that's really a TCK defect. Can we just suppress this property at the JCR layer? It would still be available for internal use but would not appear to end users. Alternatively, we should modify our definition for nt:base to include it as a protected property - this solution may violate the spec. -- 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-356) Need to Throw ItemExistsException if addNode Call Fails Due to SNS

by Brian Carothers (JIRA)

Need to Throw ItemExistsException if addNode Call Fails Due to SNS ------------------------------------------------------------------ Key: DNA-356 URL: https://jira.jboss.org/jira/browse/DNA-356 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.3 Reporter: Brian Carothers Priority: Minor According to the section 7.1.4 of the 1.0.1 specification (in the documentation for Node.addNode:) "An ItemExistsException will be thrown either immediately (by this method), or on save, if an item at the specified path already exists and same-name siblings are not allowed." DNA treats this as a generic case where no valid definition exists and throw a ConstraintViolationException. -- 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-358) Break the XmlHandler.Destination into an area where it can be reused by other importers

by Randall Hauch (JIRA)

Break the XmlHandler.Destination into an area where it can be reused by other importers --------------------------------------------------------------------------------------- Key: DNA-358 URL: https://jira.jboss.org/jira/browse/DNA-358 Project: DNA Issue Type: Task Components: API, Graph Affects Versions: 0.3 Reporter: Randall Hauch Fix For: 0.4 The XmlHandler class has a nested interface called "Destination" that provides a useful abstraction from a real graph for other kinds of importers. This and the implementations should be extracted into the "org.jboss.dna.graph.io" package, where the can be reused. The GraphImporter class could also be moved to this package, since the primary mechanism for importing XML is via Graph.importXml(...). -- 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

[JBoss JIRA] Created: (DNA-355) Wrong Exception Thrown When Creating Reference Value from Non-Referenceable Node

by Brian Carothers (JIRA)

Wrong Exception Thrown When Creating Reference Value from Non-Referenceable Node -------------------------------------------------------------------------------- Key: DNA-355 URL: https://jira.jboss.org/jira/browse/DNA-355 Project: DNA Issue Type: Bug Components: JCR Reporter: Brian Carothers Priority: Minor When invoking JcrSession.getValueFactories.createValue(Node) with a non-referenceable node as an argument, UnsupportedRepositoryOperationException is thrown (from node.getUUID(), per spec). The 1.0.1 spec for createValue(Node) indicates that it should throw a RepositoryException if its argument is not referenceable. The relevant section is 7.1.5.3 with the Javadoc: "A RepositoryException is thrown if the specified Node is not referenceable, the current Session is no longer active, or another error occurs." -- 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-354) JcrSession.hasPendingChanges Is Not Implemented

by Brian Carothers (JIRA)

JcrSession.hasPendingChanges Is Not Implemented ----------------------------------------------- Key: DNA-354 URL: https://jira.jboss.org/jira/browse/DNA-354 Project: DNA Issue Type: Bug Components: JCR Reporter: Brian Carothers Priority: Minor The JcrSession.hasPendingChanges method is currently hard-coded to return false. -- 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-353) JcrSession.exportSystemView Does Not Handle skipBinary = true Properly

by Brian Carothers (JIRA)

JcrSession.exportSystemView Does Not Handle skipBinary = true Properly ---------------------------------------------------------------------- Key: DNA-353 URL: https://jira.jboss.org/jira/browse/DNA-353 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.3 Reporter: Brian Carothers Priority: Minor Per 1.0.1 specification, exportSystemView is supposed to handle the skipBinary property like this: "If skipBinary is true then any properties of PropertyType.BINARY will be serialized as if they are empty. That is, the existence of the property will be serialized, but its content will not appear in the serialized output (the <sv:value> element will have no content). Note that in the case of multi-value BINARY properties, the number of values in the property will be reflected in the serialized output, though they will all be empty." JcrSession.exportSystemView currently omits all reference to binary properties if skipBinary is true. -- 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-352) Version Tests in SerializationTest Fail Due to TCK Bug

by Brian Carothers (JIRA)

Version Tests in SerializationTest Fail Due to TCK Bug ------------------------------------------------------ Key: DNA-352 URL: https://jira.jboss.org/jira/browse/DNA-352 Project: DNA Issue Type: Bug Components: JCR, Testing Affects Versions: 0.3 Reporter: Brian Carothers Priority: Minor The JackRabbit TCK that DNA currently uses to help gauge JCR compliance contains several tests (e.g., SerializationTest) that test whether the repository supports versioning by calling canAddMixin("mix:versionable") on a node instead of checking Repository.getDescriptor(Repository.OPTION_VERSIONING_SUPPORTED). These tests expect the canAddMixin call to return false if the repository does not support versioning. However, in section 4.11 of the 1.0.1 specification, the behavior of repositories that do not support versioning is defined differently: "A node is versionable if and only if it has been assigned the mixin type mix:versionable, otherwise it is nonversionable. Repositories that do not support versioning will simply not provide this mixin type, whereas repositories that do support versioning must provide it." Based on this, DNA needs to disable the built-in mix:versionable type. It probably makes sense to disable nt:versionHistory, nt:version, etc. as well. However, to make the tests pass, canAddMixin will need to be changed to return false when given "mix:versionable" as an argument. -- 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-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, 1 month

2
10
0 / 0

[JBoss JIRA] Created: (DNA-351) Performance Test for JCR Access

by Brian Carothers (JIRA)

Performance Test for JCR Access ------------------------------- Key: DNA-351 URL: https://jira.jboss.org/jira/browse/DNA-351 Project: DNA Issue Type: Feature Request Components: JCR, Testing Affects Versions: 0.3 Reporter: Brian Carothers Priority: Minor It may be helpful to have some performance harness in place to help test the speed of JCR read and write access in a manner analogous to the ConnectorReadableTests and ConnectorWritableTests. -- 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-350) RepoistoryNodeTypeManager.findBest*Definition Returns Wrong Definition for Protected Items if skipProtected is True.

by Brian Carothers (JIRA)

RepoistoryNodeTypeManager.findBest*Definition Returns Wrong Definition for Protected Items if skipProtected is True. -------------------------------------------------------------------------------------------------------------------- Key: DNA-350 URL: https://jira.jboss.org/jira/browse/DNA-350 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.3 Reporter: Brian Carothers Priority: Minor Currently, the RepositoryNodeTypeManager.findBest{Property|ChildNode}Definition methods have the line: if (skipProtected && definition.isProtected()) continue; The problem arises in that SessionCache.NodeEditor uses the existence of a definition as the indicator that a property can be set (and, respectively, that a child node can be added). Node types (e.g. nt:unstructured), that have a protected property (e.g., jcr:primaryType) and a residual property will return the residual definition for findBestPropertyDefinition for the property jcr:primaryType if skipProtected = true. In practice, this means that the protected property will be writable, which violates the spec and causes two TCK tests that test this condition 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues April 2009