May 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-239) code test case for SVNRepositorySource used to mange the repos. content

by Serge Emmanuel Pagop (JIRA)

code test case for SVNRepositorySource used to mange the repos. content ----------------------------------------------------------------------- Key: DNA-239 URL: https://jira.jboss.org/jira/browse/DNA-239 Project: DNA Issue Type: Sub-task Components: Connectors Affects Versions: 0.3 Reporter: Serge Emmanuel Pagop Assignee: Serge Emmanuel Pagop 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

16 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (DNA-404) Change ObservationService to use the Graph event system rather than JCR

by Randall Hauch (JIRA)

Change ObservationService to use the Graph event system rather than JCR ----------------------------------------------------------------------- Key: DNA-404 URL: https://jira.jboss.org/jira/browse/DNA-404 Project: DNA Issue Type: Task Components: Connectors, Graph, Sequencers Affects Versions: 0.4 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Blocker Fix For: 0.5 The ObservationService currently depends on a JCR implementation, but we want to remove the dependency on JCR from 'dna-repository'. See DNA-401 and DNA-252. Therefore, we need to change the ObservationService to utilize the Graph API's event system (DNA-252). This will likely require changes to the Getting Started examples and documentation. -- 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, 10 months

2
9
0 / 0

[JBoss JIRA] Created: (DNA-252) Complete support for events to the connector framework

by Randall Hauch (JIRA)

Complete support for events to the connector framework ------------------------------------------------------ Key: DNA-252 URL: https://jira.jboss.org/jira/browse/DNA-252 Project: DNA Issue Type: Task Components: Connectors Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.4 The connector's support for events is incomplete. There is the ability to add listeners to connections, but there are no methods on the listeners and no definition of what an event is. This needs to be compatible with the Requests and JCR's event 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, 10 months

1
8
0 / 0

[JBoss JIRA] Created: (DNA-102) setProperty method in SequencerOutput interface should enforce limitations on property value types

by Greg Haber (JIRA)

setProperty method in SequencerOutput interface should enforce limitations on property value types -------------------------------------------------------------------------------------------------- Key: DNA-102 URL: http://jira.jboss.com/jira/browse/DNA-102 Project: DNA Issue Type: Bug Components: API Affects Versions: 0.1, 0.2 Reporter: Greg Haber Priority: Minor The setProperty method of the SequencerOutput method, as it currently exists, accepts arbitrary single Objects or arrays of Objects as property values via its use of "Object..." in the method signature. In DNA-77, it was suggested that the current method definition should be replaced with multiple type-specific methods, but it was decided to not do this, and instead recommend use of ValueFactory to create the values used in this method. The problem with this is that, by leaving the interface as is and having use of ValueFactory be optional, it is easy for users to set properties to value types that are not currently supported (meaning that they will see a run-time error somewhere else in the code in these cases, rather than a compile-time or run-time error at the actual point where the issue was introduced (their misuse of setProperty). One possible way to enforce this in the interface is to define the interface as throwing some sort of exception if the value is not an instance of an allowed class. Another solution would be a more substantial revision of the interface to mandate use of ValueFactory to create property values. -- 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

16 years, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (DNA-401) Remove SequencingService Dependency on JCR

by Brian Carothers (JIRA)

Remove SequencingService Dependency on JCR ------------------------------------------ Key: DNA-401 URL: https://jira.jboss.org/jira/browse/DNA-401 Project: DNA Issue Type: Feature Request Components: API, Sequencers Affects Versions: 0.4 Reporter: Brian Carothers DNA currently has a circular dependency, in that the JCR project depends on the repository and graph projects (and others) as the backing store while the repository project depends on the existence of a JCR layer for the SequencingService and ObservationService. Removing the JCR dependency is tentatively planned for the ObservationService as part of DNA-252. It would be useful to remove the final piece of the circular dependency and make the SequencingService interact directly with the graph layer. As I see it, this would have the following benefits: 1. Removing a circular dependency in the architecture 2. (Ever so slightly) increasing performance by removing the expense of converting DNA nodes and properties to and from their JCR equivalents -- 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, 10 months

2
5
0 / 0

[JBoss JIRA] Updated: (DNA-55) Web Application with REST-based API for remote access and usage

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-55?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-55: ----------------------------- Fix Version/s: 0.6 (was: 0.5) Pushing all non-essential issues from 0.5 to 0.6. > Web Application with REST-based API for remote access and usage > --------------------------------------------------------------- > > Key: DNA-55 > URL: https://jira.jboss.org/jira/browse/DNA-55 > Project: DNA > Issue Type: Feature Request > Components: Server, Web Application > Reporter: Randall Hauch > Fix For: 0.6 > > > Create a DNA server that uses a REST-based API, allowing client applications to access and use the repository using HTTP for protocol/transport. > AtomPub is also very interesting (as it is RESTful) for a message structure, but it doesn't currently support hierarchical data. And although one could build a repository to be flatter (or at least exposed though collections; see how Bento does it: http://www.filemaker.com/bento/), it may be difficult to have no way of interacting with the hierarchical data. Bento and iTunes both show how powerful user-defined collections (and "smart collections") can be, so maybe adopting a collection-only approach would work (at least for remote access). -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (DNA-412) enhance the federated example to show how changes to the unified content get pushed back down to the underlying sources

by Serge Emmanuel Pagop (JIRA)

enhance the federated example to show how changes to the unified content get pushed back down to the underlying sources ----------------------------------------------------------------------------------------------------------------------- Key: DNA-412 URL: https://jira.jboss.org/jira/browse/DNA-412 Project: DNA Issue Type: Feature Request Components: Examples Affects Versions: 0.5 Reporter: Serge Emmanuel Pagop Fix For: Future Releases we need also to enhance the federated example to show how changes to the unified content get pushed back down to the underlying sources -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (DNA-409) Add to connector API ability to delete all nodes below a node

by Randall Hauch (JIRA)

Add to connector API ability to delete all nodes below a node ------------------------------------------------------------- Key: DNA-409 URL: https://jira.jboss.org/jira/browse/DNA-409 Project: DNA Issue Type: Feature Request Components: API, Connectors, Graph Affects Versions: 0.4 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.5 The federation connector requires the ability to delete all children of a parent node without knowing (or caring) which are the children. Adding a new DeleteChildrenRequest would allow this to be easily done, and RequestProcessor can even implement the process(DeleteChildrenRequest) method by reading the children and issuing a delete for each child. Although connectors would not need to know about or implement this operation, several connectors (including the JPA connector) probably should implement it anyway, because they could very efficiently do the work in one step. -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (DNA-411) JcrRepository.Options Is Plural - Coding Convention Violation

by Brian Carothers (JIRA)

JcrRepository.Options Is Plural - Coding Convention Violation ------------------------------------------------------------- Key: DNA-411 URL: https://jira.jboss.org/jira/browse/DNA-411 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.4 Reporter: Brian Carothers Priority: Trivial Fix For: 0.5 The rest of DNA is consistent in not using plurals for class names. JcrRepository.Options should be renamed. -- 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, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (DNA-400) JcrConfiguration Could Support Setting Options

by Brian Carothers (JIRA)

JcrConfiguration Could Support Setting Options ---------------------------------------------- Key: DNA-400 URL: https://jira.jboss.org/jira/browse/DNA-400 Project: DNA Issue Type: Feature Request Affects Versions: 0.4 Reporter: Brian Carothers Priority: Minor Fix For: 0.5 JcrConfiguration doesn't currently support setting the start-up options for JcrRepositories. This is needed to convert InMemoryRepositoryStub over to the configuration/engine architecture. -- 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, 10 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues May 2009