January 2010 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-628) Allow CachePolicy Configuration through Graph and Configuration Files

by Brian Carothers (JIRA)

Allow CachePolicy Configuration through Graph and Configuration Files --------------------------------------------------------------------- Key: DNA-628 URL: https://jira.jboss.org/jira/browse/DNA-628 Project: DNA Issue Type: Feature Request Components: Connectors, Graph Affects Versions: 0.6 Reporter: Brian Carothers Assignee: Brian Carothers Fix For: 1.0 The AbstractPathRepositorySource (which is used by all three of our path repository implementations) allows cache policies to be set programmatically. There needs to be a corresponding way to set the cache policy through the configuration graph (and, hence, the configuration file). -- 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

16 years

1
0
0 / 0

[JBoss JIRA] Created: (DNA-460) NodeTypeManager.unregisterType

by Brian Carothers (JIRA)

NodeTypeManager.unregisterType ------------------------------ Key: DNA-460 URL: https://jira.jboss.org/jira/browse/DNA-460 Project: DNA Issue Type: Feature Request Components: JCR Affects Versions: 0.5 Reporter: Brian Carothers Fix For: 1.0 The JSR-170 specification doesn't require (or really even mention) registering and unregistering custom node types. But since DNA supports registering node types, it seems like its pretty important to support unregistering node types as well. A swapTypes method to atomically port from one set of types to another may also be useful. -- 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

16 years

1
6
0 / 0

[JBoss JIRA] Created: (DNA-591) NullPointerException in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded()

by Barry LaFond (JIRA)

NullPointerException in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded() ----------------------------------------------------------------------------- Key: DNA-591 URL: https://jira.jboss.org/jira/browse/DNA-591 Project: DNA Issue Type: Bug Affects Versions: 0.7 Reporter: Barry LaFond Attachments: test_cnd.cnd Using the attached CND file, the repository set-up fails with an NPE when attempting to resolve node types. (ala config.repository(xxxxxx).addNodeTypes('test_cnd.cnd') java.lang.NullPointerException at org.jboss.dna.jcr.JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded(JcrNodeDefinition.java:113) at org.jboss.dna.jcr.JcrNodeDefinition.getRequiredPrimaryTypes(JcrNodeDefinition.java:161) at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1938) at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1861) at org.jboss.dna.jcr.RepositoryNodeTypeManager.registerNodeTypes(RepositoryNodeTypeManager.java:1513) at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:246) at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:161) My original DDL seqencer cnd is much more complex, but by paring it down to the following, the error still occured. //------------------------------------------------------------------------------ // N A M E S P A C E S //------------------------------------------------------------------------------ <jcr='http://www.jcp.org/jcr/1.0'> <nt='http://www.jcp.org/jcr/nt/1.0'> <mix='http://www.jcp.org/jcr/mix/1.0'> <ddl='http://jboss.org/dna/ddl/1.0'> [ddl:statement] mixin abstract - ddl:expression (string) mandatory + * (ddl:ddlProblem) = ddl:ddlProblem multiple [ddl:schemaDefinition] > ddl:statement mixin - ddl:defaultCharacterSetName (STRING) + * (ddl:ddlStatement) = ddl:ddlStatement multiple [ddl:ddlProblem] mixin - ddl:problemLevel (LONG) mandatory - ddl:message (STRING) mandatory The [ddl:schemaDefinition] mixin is the ONLY mixin that both extends a mixin and allows children of the same mixin type (i.e. [ddl:statement]) however the NPE is occuring when attempting to find the primary node type for [ddl:ddlProblem] Note that the NPE does not occur when the [ddl:schemaDefinition] type is removed. -- 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

16 years

3
11
0 / 0

[JBoss JIRA] Created: (DNA-627) Improve Support for Node Type Inheritance

by Brian Carothers (JIRA)

Improve Support for Node Type Inheritance ----------------------------------------- Key: DNA-627 URL: https://jira.jboss.org/jira/browse/DNA-627 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.6 Reporter: Brian Carothers Priority: Minor Fix For: 1.0 DNA is currently fairly conservative in when it allows node type inheritance. As just one example, the following definitions are not allowed (because type A and B both declare a child node with the same name: [nodeA] + child (nt:unstructured) [nodeB] + child (nt:unstructured) [nodeC] > nodeA, nodeB Opening this defect as a placeholder for discussion/patches around whether the inheritance rules should be relaxed and how. -- 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

16 years

1
0
0 / 0

[JBoss JIRA] Created: (DNA-618) SVN connector integration tests are failing with '404 Not Found'

by Randall Hauch (JIRA)

SVN connector integration tests are failing with '404 Not Found' ---------------------------------------------------------------- Key: DNA-618 URL: https://jira.jboss.org/jira/browse/DNA-618 Project: DNA Issue Type: Bug Components: Connectors Affects Versions: 0.7 Reporter: Randall Hauch Priority: Blocker Fix For: 0.7 This failure happened during one of the nightly integration tests. Note the '!' character in the path - is that right?? org.jboss.dna.graph.connector.RepositorySourceException: org.tmatesoft.svn.core.SVNException: svn: '/repos/dna/!svn/bc/1517/trunk/ddl_sequencer/pom.xml' path not found: 404 Not Found (http://anonsvn.jboss.org) at org.jboss.dna.graph.search.SearchEngineIndexer.checkRequestForErrors(SearchEngineIndexer.java:380) at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:265) at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227) at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135) at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334) at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292) at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593) at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257) at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175) at org.jboss.dna.test.integration.svn.SvnAndJcrIntegrationTest.beforeEach(SvnAndJcrIntegrationTest.java:72) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ... Caused by: org.tmatesoft.svn.core.SVNException: svn: '/repos/dna/!svn/bc/1517/trunk/ddl_sequencer/pom.xml' path not found: 404 Not Found (http://anonsvn.jboss.org) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getResourceProperties(DAVUtil.java:71) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getFile(DAVRepository.java:275) at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.getData(SVNRepositoryRequestProcessor.java:1351) at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.readNode(SVNRepositoryRequestProcessor.java:285) at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:308) at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:608) at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:241) at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:314) at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:223) at org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:174) at org.jboss.dna.graph.connector.RepositoryConnectionPool$ConnectionWrapper.execute(RepositoryConnectionPool.java:996) at org.jboss.dna.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:193) at org.jboss.dna.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:189) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) -- 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

16 years

2
4
0 / 0

[JBoss JIRA] Created: (DNA-610) Allow JPA Connector to be generic (not require hibernate)

by John Ament (JIRA)

Allow JPA Connector to be generic (not require hibernate) --------------------------------------------------------- Key: DNA-610 URL: https://jira.jboss.org/jira/browse/DNA-610 Project: DNA Issue Type: Feature Request Components: Connectors Affects Versions: 0.6 Reporter: John Ament Priority: Minor Allowing the use of any JPA provider (not just hibernate) would make it easier to use the JPA connector on other app servers - e.g. glassfish, weblogic, etc. There is no direct dependency on hibernate's features in the jpa connector, other than using their Ejb3Configurator. It looks like the config settings could be done in such a way that the persistence.xml could be provided by the bundling application. Design of it should probably be discussed a bit more thoroughly, and hopefully come up with a way that it can be automatically bootstrapped by the container, instead of the way configuration is done now. I'm willing to provide the implementation of this if you'd like. -- 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

16 years

3
2
0 / 0

[JBoss JIRA] Created: (DNA-612) XPath position() and last() functions are not supported

by Randall Hauch (JIRA)

XPath position() and last() functions are not supported ------------------------------------------------------- Key: DNA-612 URL: https://jira.jboss.org/jira/browse/DNA-612 Project: DNA Issue Type: Bug Components: JCR, Query Affects Versions: 0.7 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Blocker Fix For: 0.7 An XPath expression that uses the 'position()' or 'last()' functions will not work. This doesn't appear to be required by the JCR 1.0 specification [1], but is required by several TCK unit tests. [1] Section 6.6.6.3 mentions "Required function support ([42] and [60] above) is limited to the functions described in 6.6.5 XPath Extensions", but 6.6.5 does not mention position() or last() -- 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

16 years

1
2
0 / 0

[JBoss JIRA] Created: (DNA-456) Add JSR-170 Observation Optional Feature

by Brian Carothers (JIRA)

Add JSR-170 Observation Optional Feature ---------------------------------------- Key: DNA-456 URL: https://jira.jboss.org/jira/browse/DNA-456 Project: DNA Issue Type: Feature Request Components: JCR Affects Versions: 0.5 Reporter: Brian Carothers Fix For: 1.0 JSR-170 defines several optional features. The observation feature would provide notification of node and property changes to registered listeners. -- 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

16 years

3
9
0 / 0

[JBoss JIRA] Updated: (DNA-46) DNA should provide a JCR 1.0 API (JSR-170) implementation

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-46?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-46: ----------------------------- Fix Version/s: 1.0 (was: 0.7) Labels: known_issue (was: ) I don't think it's critical that this issue is fixed in 0.7, but it should be fixed before the 1.0 release. Therefore, retargeting to the 1.0 release. > DNA should provide a JCR 1.0 API (JSR-170) implementation > --------------------------------------------------------- > > Key: DNA-46 > URL: https://jira.jboss.org/jira/browse/DNA-46 > Project: DNA > Issue Type: Feature Request > Components: API, JCR > Affects Versions: 0.2 > Reporter: Randall Hauch > Assignee: Randall Hauch > Priority: Critical > Fix For: 1.0 > > > DNA should provide a JCR 1.0 API (JSR-170) implementation. -- 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

16 years

1
0
0 / 0

[JBoss JIRA] Created: (DNA-563) Connectors Are Not Generating Events For Children Of Nodes Being Added Or Removed

by Dan Florian (JIRA)

Connectors Are Not Generating Events For Children Of Nodes Being Added Or Removed --------------------------------------------------------------------------------- Key: DNA-563 URL: https://jira.jboss.org/jira/browse/DNA-563 Project: DNA Issue Type: Bug Components: Connectors Affects Versions: 0.7 Reporter: Dan Florian Fix For: 0.7 If a node is created (or removed) which causes child nodes to also be created (or removed), events should be generated for those child nodes. See Section 8.3.7 of the JCR 1.0 specification. Copying, moving, and reordering of nodes, under the covers, may also add and remove nodes. See JBoss forum referenced below for more information. -- 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

16 years

3
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues January 2010