April 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-364) Session.move Is Not Implemented

by Brian Carothers (JIRA)

Session.move Is Not Implemented ------------------------------- Key: DNA-364 URL: https://jira.jboss.org/jira/browse/DNA-364 Project: DNA Issue Type: Bug Components: JCR Reporter: Brian Carothers JcrSession does not yet implement Session.move per JCR 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, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (DNA-369) Nodes Can Be Saved Without Mandatory Properties or Child Nodes Present

by Brian Carothers (JIRA)

Nodes Can Be Saved Without Mandatory Properties or Child Nodes Present ---------------------------------------------------------------------- Key: DNA-369 URL: https://jira.jboss.org/jira/browse/DNA-369 Project: DNA Issue Type: Bug Reporter: Brian Carothers Item.save() (or Session.save()) should throw a ConstraintViolationException if any of the items to be saved is missing a mandatory property or child node (per section 7.1.1.6 and SessionTest.testSaveConstraintViolationException 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, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (DNA-365) Workspace.importXml and getContentHandler Are Not Implemented

by Brian Carothers (JIRA)

Workspace.importXml and getContentHandler Are Not Implemented ------------------------------------------------------------- Key: DNA-365 URL: https://jira.jboss.org/jira/browse/DNA-365 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.3 Reporter: Brian Carothers Workspace.importXml and getContentHandler are not implemented. Adding these methods would require DNA to support direct writes (q.v. section 7.1.3.7 of the 1.0.1 specification). -- 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 months

2
6
0 / 0

[JBoss JIRA] Created: (DNA-335) DNA's NodeTypeManager implementation does not allow multiple definitions with the same name

by Randall Hauch (JIRA)

DNA's NodeTypeManager implementation does not allow multiple definitions with the same name ------------------------------------------------------------------------------------------- Key: DNA-335 URL: https://jira.jboss.org/jira/browse/DNA-335 Project: DNA Issue Type: Bug Reporter: Randall Hauch The JCR Specification (version 1.0.1) does not preclude that there may be multiple property definitions with the same name, or that there may be multiple child definitions with the same name. JCR 1.0 (version 1.0.1) DOES say that there may be multiple residual definitions with the same name. However, the draft version of the JSR-283 specification does have a new section 4.7.15 that specifically addresses and allows multiple definitions with the same name, as long as they are distinguishable from the other definitions with the same name (for property definitions, this means the type must be different; for child node definitions, this means the required primary types attribute). There are a number of places where the logic is expecting a single property definition (or child definition) given a node type and a definition name. This is obviously flawed. Also, our logic to select the "best" property definition or "best" child node definition doesn't seem to be correct, in that it tends to favor less-restricted definitions that are lower in the type hierarchy rather than very good matching definitions higher in the type hierarchy. -- 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 months

2
9
0 / 0

[JBoss JIRA] Created: (DNA-381) The Graph API should allow creating a node if it does not already exist

by Randall Hauch (JIRA)

The Graph API should allow creating a node if it does not already exist ----------------------------------------------------------------------- Key: DNA-381 URL: https://jira.jboss.org/jira/browse/DNA-381 Project: DNA Issue Type: Feature Request Components: API, Graph Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.4 The Graph API does not provide a way to create a node if it does not already exist. This capability is already supported in the connector API, so it should be available to the Graph API users. -- 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 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-380) The inflector is not lowercasing the first character in the 'camelCase(...)' method

by Randall Hauch (JIRA)

The inflector is not lowercasing the first character in the 'camelCase(...)' method ----------------------------------------------------------------------------------- Key: DNA-380 URL: https://jira.jboss.org/jira/browse/DNA-380 Project: DNA Issue Type: Bug Components: Common Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.4 The Inflector.camelCase(...) method takes a boolean to say whether the first character should be uppercased. When 'false' was provided as a parameter, the method was not lowercasing the first character (as the JavaDoc says it should). This makes Inflector.lowerCamelCase(...) not work properly when the first character is already uppercase. -- 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 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-101) potential user confusion between org.jboss.dna.spi.graph ValueFactory and ValueFormatException interfaces and similar javax.jcr interfaces

by Greg Haber (JIRA)

potential user confusion between org.jboss.dna.spi.graph ValueFactory and ValueFormatException interfaces and similar javax.jcr interfaces ------------------------------------------------------------------------------------------------------------------------------------------ Key: DNA-101 URL: http://jira.jboss.com/jira/browse/DNA-101 Project: DNA Issue Type: Feature Request Components: API Affects Versions: 0.2 Reporter: Greg Haber Priority: Trivial The new org.jboss.dna.spi.graph.ValueFactory and package org.jboss.dna.spi.graph.ValueFormatException interfaces may be potentially confusing to users that are using both DNA and the underlying JCR APIs in the same code. This is because there are interfaces with exactly the same names, and with very similar purposes (the JCR interfaces deal with instances of the javax.jcr.Value class, where the DNA interfaces are for standard Java objects), in the javax.jcr package. We should think about changing the names of the DNA interfaces to avoid such potential confusion. This is a very minor issue, I would not object if we decided to leave the interface names unchanged. -- 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 months

3
3
0 / 0

[JBoss JIRA] Created: (DNA-377) AbstractJcrNode.addNode(String relPath) Throws Wrong Exception if relPath Has Form PropertyName/NodeName

by Brian Carothers (JIRA)

AbstractJcrNode.addNode(String relPath) Throws Wrong Exception if relPath Has Form PropertyName/NodeName -------------------------------------------------------------------------------------------------------- Key: DNA-377 URL: https://jira.jboss.org/jira/browse/DNA-377 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.3 Reporter: Brian Carothers The TCK test NodeTest.testAddNodeConstraintViolationExceptionProperty fails because DNA throws a PathNotFoundException instead of a ConstraintViolationException when the test attempts to add a child node at the relative path "prop1/node2". By spec, DNA needs to throw a ConstraintViolationException if relPath contains a property. However, DNA currently only checks for the existence of a property if the relative path has more than 2 segments. -- 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 months

2
2
0 / 0

[JBoss JIRA] Created: (DNA-303) The workspace NamespaceRegistry implementation should be shared

by Randall Hauch (JIRA)

The workspace NamespaceRegistry implementation should be shared --------------------------------------------------------------- Key: DNA-303 URL: https://jira.jboss.org/jira/browse/DNA-303 Project: DNA Issue Type: Sub-task Components: API, JCR Affects Versions: 0.3 Reporter: Randall Hauch Fix For: 0.4 The JcrWorkspace class currently uses the GraphNamespaceRegistry, which implements DNA's NamespaceRegistry implementation on top of namespace mappings stored in a graph. While this works for a single ExecutionContext, having a shared implementation for multiple JcrWorkspace objects means that the update methods need to be done with the ExecutionContext of the user making the changes. This would require changing the design a fair amount. The NamespaceRegistry implementation would also need to be thread-safe. -- 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 months

1
2
0 / 0

[JBoss JIRA] Created: (DNA-301) Most state managed within the Workspace should be shared among multiple Session instances

by Randall Hauch (JIRA)

Most state managed within the Workspace should be shared among multiple Session instances ----------------------------------------------------------------------------------------- Key: DNA-301 URL: https://jira.jboss.org/jira/browse/DNA-301 Project: DNA Issue Type: Task Components: API, JCR Affects Versions: 0.3 Reporter: Randall Hauch Fix For: 0.4 Our current JcrWorkspace implementation is created to be used only by the one JcrSession instance associated with it. Currently, each Session would have it's own Workspace implementation, each of which would have its own copy of the namespace registry and node type manager. However, one common use case for JCR involves creating many Session instances for the same workspace (e.g., this is the web app scenario). This means that we'd have a lot of Workspace instances (same number as Session instances) each with their own copy of the data. In fact, the node type manager should actually be "owned" (at least logically) by the repository, per section 6.7.9: "There is one node type registry per repository, therefore the NodeTypeManager is not workspace-specific; it provides introspection methods for the global, repository-wide set of available node types." Therefore, a number of things that are currently in the JcrWorkspace implementation should be pulled out and reused for all JcrWorkspace instances created by the JcrRepository for the same logical workspace. This issue captures the set of tasks that are involved. -- 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 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues April 2009