July 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-448) The 'createIfMissing()' methods should be removed from the Graph API

by Randall Hauch (JIRA)

The 'createIfMissing()' methods should be removed from the Graph API -------------------------------------------------------------------- Key: DNA-448 URL: https://jira.jboss.org/jira/browse/DNA-448 Project: DNA Issue Type: Bug Components: API, Graph Affects Versions: 0.4 Reporter: Randall Hauch Fix For: 0.6 This issue stemmed from DNA-443. The existence of the "createIfMissing()" methods that exist only on the Graph interface (and not the Graph.Batch interface) mask the existence of newer, more powerful methods that can do the same thing on Graph and Graph.Batch: graph.create(path).ifAbsent()... or batch.create(path).ifAbsent()... In fact, this style makes available several other methods than "ifAbsent()", such as "orUpdate()", "byAppending()", and "orReplace()". These correspond to the different NodeConflictBehavior options. Unfortunately, the 'create()' methods just return the Conjunction interface, while the 'createIfMissing()' methods return the "GetNodeConjunction" interface (which extends Conjunction and adds the "andReturn():Node" method). And there is at least one place where 'createIfMissing(...).andReturn()' is being called. Looking at this now, I'm not sure why the Graph.create(...) methods can't return the GetNodeConjunction interface. This would allow the existing uses of the 'createIfMissing(...).andReturn()' to replace them with 'create(...).ifAbsent().andReturn()' calls, and enable the removal of the 'createIfMissing(...)' methods. -- 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

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (DNA-487) Add integration test that uses the Infinispan connector

by Brian Carothers (JIRA)

Add integration test that uses the Infinispan connector ------------------------------------------------------- Key: DNA-487 URL: https://jira.jboss.org/jira/browse/DNA-487 Project: DNA Issue Type: Sub-task Components: Connectors, Testing Affects Versions: 0.5 Reporter: Brian Carothers -- 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

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-477) Add integration test that uses the JBoss Cache connector

by Randall Hauch (JIRA)

Add integration test that uses the JBoss Cache connector -------------------------------------------------------- Key: DNA-477 URL: https://jira.jboss.org/jira/browse/DNA-477 Project: DNA Issue Type: Sub-task Affects Versions: 0.5 Reporter: Randall Hauch Fix For: 0.6 Add a test that uses the JBoss Cache connector. -- 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

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (DNA-488) Revamp TCK testing infrastructure to support running against multiple configurations

by Brian Carothers (JIRA)

Revamp TCK testing infrastructure to support running against multiple configurations ------------------------------------------------------------------------------------ Key: DNA-488 URL: https://jira.jboss.org/jira/browse/DNA-488 Project: DNA Issue Type: Sub-task Components: JCR, Testing Affects Versions: 0.5 Reporter: Brian Carothers -- 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

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (DNA-482) Make nt:unstructured be the default primary type (but not the required primary type) for the residual item definition in dna:root, the type of the root node

by Serge Emmanuel Pagop (JIRA)

Make nt:unstructured be the default primary type (but not the required primary type) for the residual item definition in dna:root, the type of the root node ------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: DNA-482 URL: https://jira.jboss.org/jira/browse/DNA-482 Project: DNA Issue Type: Feature Request Components: JCR Affects Versions: 0.6, 1.0, Future Releases Reporter: Serge Emmanuel Pagop Fix For: Future Releases I tried some code with the new jcr data mass generator and I got an javax.jcr.nodetype.ConstraintViolationException, because I forgot to include primary type nt:unstructured during addNode. The same ran well on JR without any setting of primary type nt:unstructured. consecution, there is a deviation between the JR impl. behavior and the DNA JRC impl. -- 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

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (DNA-474) Add Inifinispan Connector

by Brian Carothers (JIRA)

Add Inifinispan Connector ------------------------- Key: DNA-474 URL: https://jira.jboss.org/jira/browse/DNA-474 Project: DNA Issue Type: Feature Request Components: Connectors Affects Versions: 0.5 Reporter: Brian Carothers It might be useful to have a connector for Infinispan with a set of features comparable to what's currently available for the JBoss Cache connector. -- 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

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (DNA-485) Standardize Default Workspace Name Property Across Sources

by Brian Carothers (JIRA)

Standardize Default Workspace Name Property Across Sources ---------------------------------------------------------- Key: DNA-485 URL: https://jira.jboss.org/jira/browse/DNA-485 Project: DNA Issue Type: Feature Request Components: API, Connectors Affects Versions: 0.5 Reporter: Brian Carothers Priority: Minor Most (if not all) repositories will likely have the concept of a default workspace that has a configurable name. The in-memory, JBoss Cache, and Infinispan repositories already have this feature. However, they use different names for the property on the repository source object (in-memory -> defaultWorkspaceName, JBC -> nameOfDefaultWorkspace, Infinispan -> nameOfDefaultWorkspace). Strictly speaking, this is a syntactically acceptable approach, but from a usability standpoint, it makes sense to establish naming conventions for common property names. Since the in-memory repository is very widely used in the codebase already, it probably makes the most sense to standardize on "defaultWorkspaceName" as the property containing the name of the default workspace. -- 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

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (DNA-484) Repository Startup Errors Use String[].toString() in Error Message

by Brian Carothers (JIRA)

Repository Startup Errors Use String[].toString() in Error Message ------------------------------------------------------------------ Key: DNA-484 URL: https://jira.jboss.org/jira/browse/DNA-484 Project: DNA Issue Type: Bug Components: Graph Affects Versions: 0.5 Reporter: Brian Carothers Priority: Minor If one attempts to create a repository based on a source that is not in the classpath and one applies the patch to expose the startup problems, one will get a message like this: ERROR: Unable to load class "org.jboss.dna.graph.connector.jbosscache.JBossCacheSource" using classpath "[Ljava.lang.String;@9444d1" (threw org.jboss.dna.graph.connector.jbosscache.JBossCacheSource) The classpath String[] argument is being printed directly instead of being converted to a list first to handle the pretty-printing. -- 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

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (DNA-481) Correct path to node types under "/jcr:system"

by Randall Hauch (JIRA)

Correct path to node types under "/jcr:system" ---------------------------------------------- Key: DNA-481 URL: https://jira.jboss.org/jira/browse/DNA-481 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.5 Reporter: Randall Hauch Priority: Blocker Fix For: 0.6 The changes to DNA-466 included a correction to use "/jcr:system/dna:nodeTypes", since that is what was in the DNA built-in node types (CND file). Although JSR-170 doesn't expose the node types under "/jcr:system", JSR-283 specifies the path of "/jcr:system/jcr:nodeTypes" (note the namespace change). Our code should be changed to reflect this. -- 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

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (DNA-480) Clean up compiler warnings

by Randall Hauch (JIRA)

Clean up compiler warnings -------------------------- Key: DNA-480 URL: https://jira.jboss.org/jira/browse/DNA-480 Project: DNA Issue Type: Task Components: Graph, JCR Affects Versions: 0.5 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Blocker Fix For: 0.6 Read access to enclosing field Graph.CloneAction<T>.from is emulated by a synthetic accessor method. Increasing its visibility will improve your performance Graph.java dna-graph/src/main/java/org/jboss/dna/graph line 6227 Read access to enclosing field Graph.CloneAction<T>.from is emulated by a synthetic accessor method. Increasing its visibility will improve your performance Graph.java dna-graph/src/main/java/org/jboss/dna/graph line 6238 The declared exception SAXException is not actually thrown by the method addNodeIfPending() from type JcrContentHandler.SystemViewContentHandler JcrContentHandler.java dna-jcr/src/main/java/org/jboss/dna/jcr line 302 The declared exception SAXException is not actually thrown by the method characters(char[], int, int) from type JcrContentHandler.DocumentViewContentHandler JcrContentHandler.java dna-jcr/src/main/java/org/jboss/dna/jcr line 501 The declared exception SAXException is not actually thrown by the method startElement(String, String, String, Attributes) from type JcrContentHandler.DocumentViewContentHandler JcrContentHandler.java dna-jcr/src/main/java/org/jboss/dna/jcr line 419 The method addNodeToMap(MapNode) of type InMemoryRepository.Workspace should be tagged with @Override since it actually overrides a superclass method InMemoryRepository.java dna-graph/src/main/java/org/jboss/dna/graph/connector/inmemory line 73 The method addNodeToMap(MapNode) of type JBossCacheRepository.Workspace should be tagged with @Override since it actually overrides a superclass method JBossCacheRepository.java dna-connector-jbosscache/src/main/java/org/jboss/dna/connector/jbosscache line 59 The method createWorkspace(ExecutionContext, String) of type InMemoryRepository should be tagged with @Override since it actually overrides a superclass method InMemoryRepository.java dna-graph/src/main/java/org/jboss/dna/graph/connector/inmemory line 58 The method getNode(UUID) of type InMemoryRepository.Workspace should be tagged with @Override since it actually overrides a superclass method InMemoryRepository.java dna-graph/src/main/java/org/jboss/dna/graph/connector/inmemory line 88 The method getNode(UUID) of type JBossCacheRepository.Workspace should be tagged with @Override since it actually overrides a superclass method JBossCacheRepository.java dna-connector-jbosscache/src/main/java/org/jboss/dna/connector/jbosscache line 73 The method removeAllNodesFromMap() of type InMemoryRepository.Workspace should be tagged with @Override since it actually overrides a superclass method InMemoryRepository.java dna-graph/src/main/java/org/jboss/dna/graph/connector/inmemory line 84 The method removeAllNodesFromMap() of type JBossCacheRepository.Workspace should be tagged with @Override since it actually overrides a superclass method JBossCacheRepository.java dna-connector-jbosscache/src/main/java/org/jboss/dna/connector/jbosscache line 69 The method removeNodeFromMap(UUID) of type InMemoryRepository.Workspace should be tagged with @Override since it actually overrides a superclass method InMemoryRepository.java dna-graph/src/main/java/org/jboss/dna/graph/connector/inmemory line 79 The method removeNodeFromMap(UUID) of type JBossCacheRepository.Workspace should be tagged with @Override since it actually overrides a superclass method JBossCacheRepository.java dna-connector-jbosscache/src/main/java/org/jboss/dna/connector/jbosscache line 64 -- 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

14 years, 11 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues July 2009