April 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-282) Federation connector improperly handles root-level node with one projection of a non-root node from a single source

by Randall Hauch (JIRA)

Federation connector improperly handles root-level node with one projection of a non-root node from a single source ------------------------------------------------------------------------------------------------------------------- Key: DNA-282 URL: https://jira.jboss.org/jira/browse/DNA-282 Project: DNA Issue Type: Bug Components: Connectors Reporter: Randall Hauch Assignee: Randall Hauch Priority: Blocker The federation connector currently has a problem when configured to project a non-root node from a single source into the root node of the federated repository. The cache always has a root node with a specific UUID, and the single source's non-root node has a different UUID, so when the federation connector attempts to project that non-root node from the source into the root node of the federated repository, the cache is unable to store the node with the UUID from the source. This problem arose when working on DNA-281 - the test cases were changed to use the InMemory connector rather than the SimpleRepositorySource connector (used for testing only). The simple implementation didn't maintain UUIDs, whereas the in-memory implementation does. (This is one of the problems with using a "mock" or non-production implementation in tests.) So, although the code compiles, several of the federation connector's tests fail, and the problem also affects several of the JCR unit tests and the Getting Started repository example. Therefore, after these are fixed, the corresponding projects need to be added back into the POM 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

15 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (DNA-384) Trouble compiling Java sequencer using Eclipse JDT and its dependencies

by Randall Hauch (JIRA)

Trouble compiling Java sequencer using Eclipse JDT and its dependencies ----------------------------------------------------------------------- Key: DNA-384 URL: https://jira.jboss.org/jira/browse/DNA-384 Project: DNA Issue Type: Bug Components: Sequencers Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.4 The "dna-sequencer-java" project compiles with errors with newer versions of the Eclipse JDT because of dependency issues (some dependencies are not in the JBoss Maven 2 repository). -- 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-366) Allow child node to be reordered in the Graph API

by Randall Hauch (JIRA)

Allow child node to be reordered in the Graph API ------------------------------------------------- Key: DNA-366 URL: https://jira.jboss.org/jira/browse/DNA-366 Project: DNA Issue Type: Feature Request Components: API, Connectors, Graph Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.4 The Graph API doesn't really allow the child nodes to be reordered. This feature is required for the JCR 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

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-383) dna-jcr-tck Project Keeps Getting Out Of Sync With dna-jcr Project

by Brian Carothers (JIRA)

dna-jcr-tck Project Keeps Getting Out Of Sync With dna-jcr Project ------------------------------------------------------------------ Key: DNA-383 URL: https://jira.jboss.org/jira/browse/DNA-383 Project: DNA Issue Type: Bug Components: JCR, Testing Affects Versions: 0.3 Reporter: Brian Carothers Priority: Minor Fix For: 0.4 The dna-jcr-tck project currently has its own local copy of the InMemoryRepositoryStub and repositoryStubImpl.properties. If these two files are not kept in sync with their corresponding copies in dna-jcr, the TCK tests results will skew (generally in a negative direction). It would be helpful to either keep syncing them up or remove the redundant files and fix the dependencies. -- 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-374) Multiplicity of some properties may change when saved and reloaded from the graph

by Randall Hauch (JIRA)

Multiplicity of some properties may change when saved and reloaded from the graph --------------------------------------------------------------------------------- Key: DNA-374 URL: https://jira.jboss.org/jira/browse/DNA-374 Project: DNA Issue Type: Bug Components: JCR Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.4 This problem arises when a client uses the multi-valued setter methods in the JCR API to create on a node a new property with a single value, to save the node, and then to continue working with the property (again, using the multi-valued setter or getter methods). When the property is created, an appropriate multi-valued property definition will be chosen from those available on the node's primary type (and mixin types, if there are any). However, after the save, the property may node have a single-valued property definition. And since JCR does not allow a single-valued property to be changed via the multi-valued setters, the result is an exception when the client attempts to set the property using the multi-valued setters. -- 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
5
0 / 0

[JBoss JIRA] Created: (DNA-382) Workspace.move Is Not Supported

by Brian Carothers (JIRA)

Workspace.move Is Not Supported ------------------------------- Key: DNA-382 URL: https://jira.jboss.org/jira/browse/DNA-382 Project: DNA Issue Type: Bug Affects Versions: 0.3 Reporter: Brian Carothers JcrWorkspace.move is stubbed in. -- 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
3
0 / 0

[JBoss JIRA] Updated: (DNA-37) Federate schema information from relational sources

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-37?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-37: ----------------------------- Fix Version/s: 0.5 (was: 0.4) Pushing to 0.5, since they are not critical for 0.4 and because we're approaching the end of 0.4. If the assignee thinks it can be finished before the 0.4 release, please note here and notify the team. > Federate schema information from relational sources > --------------------------------------------------- > > Key: DNA-37 > URL: https://jira.jboss.org/jira/browse/DNA-37 > Project: DNA > Issue Type: Feature Request > Components: Connectors > Reporter: Randall Hauch > Assignee: Sergiy Litsenko > Priority: Minor > Fix For: 0.5 > > > Create a connector for the federation engine that contributes and exposes the database schema information for a relational database (via JDBC) into the federated repository. This would make it possible to have a repository provide information about the databases in an organization. One choice would be whether to import (and copy) the schema structure, or to provide access to it in real time. -- 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
0
0 / 0

[JBoss JIRA] Updated: (DNA-36) Federate content from SVN

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-36?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-36: ----------------------------- Fix Version/s: 0.5 (was: 0.4) Pushing to 0.5, since they are not critical for 0.4 and because we're approaching the end of 0.4. If the assignee thinks it can be finished before the 0.4 release, please note here and notify the team. > Federate content from SVN > ------------------------- > > Key: DNA-36 > URL: https://jira.jboss.org/jira/browse/DNA-36 > Project: DNA > Issue Type: Feature Request > Components: Connectors > Affects Versions: 0.4 > Reporter: Randall Hauch > Assignee: Serge Emmanuel Pagop > Priority: Minor > Fix For: 0.5 > > > Create a connector for the federation engine that contributes and exposes content stored in a source control management (SCM) system into the federated repository. This would enable integration of files managed by SVN (or CVS, etc.) to be accessible via JCR. -- 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
0
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: 0.5 (was: 0.4) Pushing to 0.5, since DNA-285 was also pushed. We've made gargantuan progress in 0.4, but we do have a few things left. > 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: 0.5 > > > 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

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (DNA-194) Implement update JCR capability

by Johnny Verhaeg (JIRA)

Implement update JCR capability ------------------------------- Key: DNA-194 URL: https://jira.jboss.org/jira/browse/DNA-194 Project: DNA Issue Type: Sub-task Components: JCR Reporter: Johnny Verhaeg Fix For: 0.3 -- 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

3
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues April 2009