August 2008 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-191) Move sequencer, connector, and MIME type detector projects into an "extensions" folder (under trunk)

by Randall Hauch (JIRA)

Move sequencer, connector, and MIME type detector projects into an "extensions" folder (under trunk) ---------------------------------------------------------------------------------------------------- Key: DNA-191 URL: https://jira.jboss.org/jira/browse/DNA-191 Project: DNA Issue Type: Task Components: Connectors, Maven Classloader, Sequencers Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.2 DNA 0.1 introduced the concept of a sequencer, and we created a "sequencers" folder (under trunk) where we've been putting the projects that provide sequencer implementations. With DNA 0.2, we've also introduced the concept of a connector and - not surprisingly - placed all of the connector implementations in projects under a "connectors" folder (under trunk). Recently we introduced a third kind of extension point: the MIME type detector. We currently have only one implementation, but there certainly is the possibility that we'll have more. And really, the "dna-maven-classloader" is another type of extension. But three different types of "extensions" doth make a pattern, and I wouldn't be surprised if we have more. Rather than have different folders under trunk for these different types of extensions, I'd like to make a single "extensions" folder (under trunk) and move all sequencer, connector, MIME type detector, and Maven class loader projects into that one folder. The project naming convention helps keep things clearly identified, all of these extensions really are optional (easier to describe in the documentation), we'll simplify the directory organization, and it will make it easier if any extension project wants to provide more than one type of extension (say, a detector AND a sequencer). Pinging the dna-dev@ list to see when might be a good time to schedule 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

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-83) Federate content from JBoss Cache instance(s)

by Randall Hauch (JIRA)

Federate content from JBoss Cache instance(s) --------------------------------------------- Key: DNA-83 URL: http://jira.jboss.com/jira/browse/DNA-83 Project: DNA Issue Type: Feature Request Components: Connectors Reporter: Randall Hauch Assigned To: Randall Hauch Fix For: 0.2 Create a federation connector that provides access to information stored in a JBoss Cache instance. The content (nodes with data) would be mapped directly to nodes with properties. -- 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

17 years, 2 months

1
9
0 / 0

[JBoss JIRA] Created: (DNA-192) Clean up the repository connector SPI

by Randall Hauch (JIRA)

Clean up the repository connector SPI ------------------------------------- Key: DNA-192 URL: https://jira.jboss.org/jira/browse/DNA-192 Project: DNA Issue Type: Task Components: Connectors, SPI Affects Versions: 0.2 Reporter: Randall Hauch Fix For: 0.2 The current SPI is somewhat confusing, especially the distinction between RepositoryConnectionFactory and RepositorySource, and what the meaning of the RepositoryConnectionFactories interface is. The original idea was to pattern after JDBC DataSource, but a number of things are not handled well in DataSource (like connection pooling, which is done above the sources). Plus, the current design extracted interfaces when there was similar behavior/methods rather than designing the interfaces to be easily understood and used, and this resulted in some confusing names and concepts that overlapped or were too generic. There should be a RepositorySource interface that defines all of the methods: getName(), getConnection(), and the management methods like shutdown(), shutdownNow(), isShutdown(), isTerminated(), awaitTermination(), etc. Also, if a RepositorySource would benefit from pooling connections, it should implement the pooling and can include any pooling parameters in the source's JavaBean properties. This means that no pooling is ever done above the RepositorySource, and that the RepositorySource bean properties fully specify and control the behavior of the source. To make it easier to implement RepositorySource with pooling, the RepositoryConnectionPool class should be kept but should not share any interfaces, and an AbstractRepositorySource implement most of the RepositorySource functionality by delegating to a pool that it owns and manages. -- 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

17 years, 2 months

1
6
0 / 0

[JBoss JIRA] Created: (DNA-179) Add generation of maven dependencies report to the nightly and continuous Hudson jobs

by Randall Hauch (JIRA)

Add generation of maven dependencies report to the nightly and continuous Hudson jobs ------------------------------------------------------------------------------------- Key: DNA-179 URL: https://jira.jboss.org/jira/browse/DNA-179 Project: DNA Issue Type: Task Components: Development Environment Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.2 The Maven dependency report is a useful report that shows the (deep) dependencies of the DNA projects. This report should be added to the nightly and continuous integration jobs in Hudson. -- 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

17 years, 2 months

1
6
0 / 0

[JBoss JIRA] Created: (DNA-196) Add methods to ValueFactory that takes Iterator<?> and returns Iterator<T>

by Randall Hauch (JIRA)

Add methods to ValueFactory that takes Iterator<?> and returns Iterator<T> -------------------------------------------------------------------------- Key: DNA-196 URL: https://jira.jboss.org/jira/browse/DNA-196 Project: DNA Issue Type: Task Components: SPI Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.2 Since Property.getValues() returns Iterator<?>, ValueFactory should have methods that accept that Iterator<?> and returns an Iterator<T>. This would make it easier to use the factory to get the value(s) out of a Property in the type that you want (without having to cast and with proper conversion if required). -- 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

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-195) create in test directory a workspace for test data

by Serge Emmanuel Pagop (JIRA)

create in test directory a workspace for test data -------------------------------------------------- Key: DNA-195 URL: https://jira.jboss.org/jira/browse/DNA-195 Project: DNA Issue Type: Sub-task Components: Sequencers Affects Versions: 0.2 Reporter: Serge Emmanuel Pagop Fix For: 0.2 -- 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

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-193) Add methods to ExecutionContext and ExecutionContextFactory to support JAAS

by Johnny Verhaeg (JIRA)

Add methods to ExecutionContext and ExecutionContextFactory to support JAAS --------------------------------------------------------------------------- Key: DNA-193 URL: https://jira.jboss.org/jira/browse/DNA-193 Project: DNA Issue Type: Sub-task Reporter: Johnny Verhaeg Assignee: Johnny Verhaeg -- 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

17 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (DNA-87) Create rough Repository, Workspace, Session and Node implementations (with stubs for many methods and other interfaces)

by Randall Hauch (JIRA)

Create rough Repository, Workspace, Session and Node implementations (with stubs for many methods and other interfaces) ----------------------------------------------------------------------------------------------------------------------- Key: DNA-87 URL: http://jira.jboss.com/jira/browse/DNA-87 Project: DNA Issue Type: Sub-task Components: API Reporter: Randall Hauch Assigned To: Randall Hauch Fix For: 0.2 Create initial (and rough) implementations of the Repository, Workspace, Session and Node interfaces. The primary goal is to set up the components on top of the federation engine to provide feedback to the graph SPI and federation engine design. -- 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

17 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (DNA-86) Create Maven project for JCR API implementation

by Randall Hauch (JIRA)

Create Maven project for JCR API implementation ----------------------------------------------- Key: DNA-86 URL: http://jira.jboss.com/jira/browse/DNA-86 Project: DNA Issue Type: Sub-task Components: API Affects Versions: 0.2 Reporter: Randall Hauch Assigned To: Randall Hauch Create the Maven 2 child project "dna-jcr" and add to the parent POM. -- 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

17 years, 2 months

2
2
0 / 0

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

by Johnny Verhaeg (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-46?page=com.atlassian.jira.plugin.... ] Johnny Verhaeg updated DNA-46: ------------------------------ Summary: DNA should provide a JCR 1.0 API (JSR-170) implementation (was: Federation engine should support JCR 1.0 (JSR-170) API) Component/s: JCR (was: Federation) Description: DNA should provide a JCR 1.0 API (JSR-170) implementation. (was: The federation engine should implement the JCR 1.0 API (JSR-170).) > 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 > Reporter: Randall Hauch > Assignee: Johnny Verhaeg > Priority: Critical > Fix For: 0.2 > > > 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

17 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues August 2008