January 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-276) ExecutionContext story should be simplified by eliminating ExecutionContextFactory

by Johnny Verhaeg (JIRA)

ExecutionContext story should be simplified by eliminating ExecutionContextFactory ---------------------------------------------------------------------------------- Key: DNA-276 URL: https://jira.jboss.org/jira/browse/DNA-276 Project: DNA Issue Type: Feature Request Components: Graph Affects Versions: 0.3 Reporter: Johnny Verhaeg Fix For: 0.4 The relationship between the concrete ExecutionContext class and its implemented ExecutionContextFactory interface is a bit confusing and non-intuitive. In particular, it's not really clear without understanding the implementation of ExecutionContext when to use the ExecutionContext constructor vs. the factory's create methods. The factory should be eliminated, and the relevant "create" methods in the context should be changed to "with" methods, mimicking the other existing, more readable pattern used by ExecutionContext to, for instance, create a context with a different namespace registry. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (DNA-261) Improve how Binary values are created and managed

by Randall Hauch (JIRA)

Improve how Binary values are created and managed ------------------------------------------------- Key: DNA-261 URL: https://jira.jboss.org/jira/browse/DNA-261 Project: DNA Issue Type: Feature Request Components: Graph Reporter: Randall Hauch Priority: Minor Fix For: 0.4 The current InMemoryBinaryValueFactory is creating separate InMemoryBinary objects each time 'create(...)' is called. We should have a Binary factory (and corresponding Binary implementations) that caches the in-memory values using the content's hash as a key. While this may slightly degrade performance (since the hash would be computed immediately rather than lazily if needed), it could result in more efficient use of memory. Note that we'd probably have to use weak or soft references inside the Binary object to the cached values, so that as the Binary objects are garbage collected, the cache can remove the unused values. Another potential improvement is to store large values on disk, and to memory-map them using direct buffers. This would keep large values (e.g., gigabyte-sized values, such as those used to represent very large files) out of memory. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Assigned: (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 reassigned DNA-46: -------------------------------- Assignee: Randall Hauch (was: Johnny Verhaeg) > 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.4 > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (DNA-273) Define and document the official patch procedure

by Randall Hauch (JIRA)

Define and document the official patch procedure ------------------------------------------------ Key: DNA-273 URL: https://jira.jboss.org/jira/browse/DNA-273 Project: DNA Issue Type: Task Reporter: Randall Hauch Fix For: 0.4 We need to define our patch procedure so that it does not involve Eclipse patches, but rather uses standard patches that are compatible with SVN. We then need to document this procedure in the Reference Guide. -- 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, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (DNA-272) Move the In-Memory connector into "dna-graph"

by Randall Hauch (JIRA)

Move the In-Memory connector into "dna-graph" --------------------------------------------- Key: DNA-272 URL: https://jira.jboss.org/jira/browse/DNA-272 Project: DNA Issue Type: Task Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.4 The "in-memory" connector implementation is a good transient repository store, and having a transient store in "dna-graph" will simplify a number of things. Right now, the only connectors are in extensions, so the core libraries (e.g., "dna-graph", "dna-repository", etc.) do not have access to any connector implementation, making it difficult to set up a default source. For example, I'm working on a new configuration component in "dna-repository" that will set up all the DNA services, and the configuration component works by populating a configuration repository. By default, the configuration component would instantiate a transient configuration repository, but there isn't an implementation available. (The configuration component will also allow setting up the configuration repository, so one can use a remote source.) -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-271) Change mechanism to declare copyright, moving from source code into separate file included with distributions

by Randall Hauch (JIRA)

Change mechanism to declare copyright, moving from source code into separate file included with distributions ------------------------------------------------------------------------------------------------------------- Key: DNA-271 URL: https://jira.jboss.org/jira/browse/DNA-271 Project: DNA Issue Type: Task Components: API, Common, Connectors, Development Environment, Documentation, Examples, Federation, Graph, JCR, Maven Classloader, Sequencers, Testing Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Minor Fix For: 0.4 Attachments: AUTHORS.txt, COPYRIGHT.txt The copyright information in our source needs to be cleaned up and corrected. In particular, we can place the copyright into a separate COPYRIGHT.txt file included in each distribution, and change the headers to refer to this file. Then the source only contains the license information (plus references to the copyright and authors files in the distribution). This is actually a much better way to handle copyrights (since the year and the copyright text is in one place, and can be annotated as required), yet does not change any rights on existing code. Also, SVN is the master record for each individual contribution, so pending decision by the community, the "@author" tags would be removed from the code, which would refer to a new AUTHORS.txt file. The content of the AUTHORS.txt, COPYRIGHT.txt, and new header are attached. Note that the Eclipse preferences need to be changed accordingly. -- 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, 3 months

1
5
0 / 0

[JBoss JIRA] Created: (DNA-275) Change plural package names to be singular

by Randall Hauch (JIRA)

Change plural package names to be singular ------------------------------------------ Key: DNA-275 URL: https://jira.jboss.org/jira/browse/DNA-275 Project: DNA Issue Type: Task Components: API Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Minor Fix For: 0.4 We have several cases where we're using package names that are plural. Many style guides recommend using singular nouns. Above all, we need to be consistent (which we're not). It's better to make these changes now rather than later. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-270) Simplify the ExecutionContext framework

by Randall Hauch (JIRA)

Simplify the ExecutionContext framework --------------------------------------- Key: DNA-270 URL: https://jira.jboss.org/jira/browse/DNA-270 Project: DNA Issue Type: Task Components: API, Connectors, Documentation, Examples, Graph, Sequencers Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.4 The ExecutionContext interface is used throughout the system. It's defined in 'dna-graph', and used to represent the context or environment for executing various activities. There is also ExecutionContextFactory, which is an interface for creating other contexts with different JAAS security contexts (login context or access control contexts). There are also the Basic* implementations of these interfaces, as well as several subclasses (with various implementations). The idea of using an interface for this was to simplify the design of the components that uses/took an ExecutionContext, to prevent propagating dependencies, and to allow customization. However, since ExecutionContext is largely just an aggregation of references, there's little need to customize the behavior, and this doesn't really add any other dependencies to the classpath (all implementations of the aggregated components are already in 'dna-graph') and it doesn't expose any implementations through the method signatures. Using interfaces also complicates the usage, since clients have to know about the concrete implementations. This is even more true when they're setting up the DNA services and repositories in 'dna-repository' and 'dna-jcr'. So, consider changing this interface to a concrete class, with methods that make it easy to create instances as well as instances with custom components (e.g., a new context that is the same as 'this' but with a supplied NamespaceRegistry implementation). This will change the public API, but this should be acceptable given that we're not yet at 1.0 (and this really improves both the client code, and doesn't really change extension implementations). -- 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, 3 months

1
7
0 / 0

[JBoss JIRA] Resolved: (DNA-34) Federate content stored on file system (read-only access)

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-34?page=com.atlassian.jira.plugin.... ] Randall Hauch resolved DNA-34. ------------------------------ Resolution: Done Completed the file system connector and read support. Added unit test that uses the standard connector read tests. Also fixed a bug in the AbstractValueFactory that neglected to look for a Binary object in "create(Object)". > Federate content stored on file system (read-only access) > --------------------------------------------------------- > > Key: DNA-34 > URL: https://jira.jboss.org/jira/browse/DNA-34 > Project: DNA > Issue Type: Feature Request > Components: Connectors > Reporter: Randall Hauch > Assignee: Randall Hauch > Fix For: 0.4 > > > Create a connector for the federation engine that contributes and exposes content stored on the file system (in one or more directories) into the federated repository. This connector would dynamically create the "nt:file" and "nt:folder" nodes to mirror the contents of the file system. The initial implementation only needs to support reading. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (DNA-34) Federate content stored on file system (read-only access)

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-34?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-34: ----------------------------- Summary: Federate content stored on file system (read-only access) (was: Federate content stored on file system) Description: Create a connector for the federation engine that contributes and exposes content stored on the file system (in one or more directories) into the federated repository. This connector would dynamically create the "nt:file" and "nt:folder" nodes to mirror the contents of the file system. The initial implementation only needs to support reading. (was: Create a connector for the federation engine that contributes and exposes content stored on the file system (in one or more directories) into the federated repository. This connector would dynamically create the "nt:file" and "nt:folder" nodes to mirror the contents of the file system.) > Federate content stored on file system (read-only access) > --------------------------------------------------------- > > Key: DNA-34 > URL: https://jira.jboss.org/jira/browse/DNA-34 > Project: DNA > Issue Type: Feature Request > Components: Connectors > Reporter: Randall Hauch > Assignee: Randall Hauch > Fix For: 0.4 > > > Create a connector for the federation engine that contributes and exposes content stored on the file system (in one or more directories) into the federated repository. This connector would dynamically create the "nt:file" and "nt:folder" nodes to mirror the contents of the file system. The initial implementation only needs to support reading. -- 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, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues January 2009