July 2008 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-62) Sequence JAR files to extract class structure and annotations

by Randall Hauch (JIRA)

Sequence JAR files to extract class structure and annotations ------------------------------------------------------------- Key: DNA-62 URL: http://jira.jboss.com/jira/browse/DNA-62 Project: DNA Issue Type: Feature Request Components: Sequencers Reporter: Randall Hauch Fix For: 0.2 This use case comes from a discussion about starting up the Microcontainer, and the desire to have a single processor of the JAR files to extract into a centralized repository the runtime annotations. Right now the annotations are scanned by each component/service that needs them. This feature would obviate the scanning being done by each component/service. Consider using http://scannotation.sourceforge.net/ for doing the actual scanning. -- 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

14 years, 3 months

2
12
0 / 0

[JBoss JIRA] Created: (DNA-159) Federate/cache content from a remote JCR (and DNA) repository

by Randall Hauch (JIRA)

Federate/cache content from a remote JCR (and DNA) repository ------------------------------------------------------------- Key: DNA-159 URL: http://jira.jboss.com/jira/browse/DNA-159 Project: DNA Issue Type: Feature Request Components: Connectors Reporter: Randall Hauch Priority: Minor Fix For: Future Releases The primary use case for this feature is to allow an application to have a local DNA repository that is configured to be a local, cached copy of a single remote JCR repository. So, rather than having multiple sources, this use case would have a single source (using a connector to a remote JCR repository), and it would be configured to probably have a cache policy with a relatively short TTL. (Of course the TTL could be extended if the connector could listen to the remote repository to receive events, which would be propagated up to the local "federated" repository and would cause those particular changed instances to be purged from the cache. Ideally this could be made to be very lightweight and very easy to configure, maybe even using just an in-memory "integrated repository" (aka, cache). This use case is far superior to an implementation that uses remote calls for every operation. -- 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

14 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-105) Sequence metadata from delimited text files

by Greg Haber (JIRA)

Sequence metadata from delimited text files ------------------------------------------- Key: DNA-105 URL: http://jira.jboss.com/jira/browse/DNA-105 Project: DNA Issue Type: Feature Request Components: Sequencers Reporter: Greg Haber Priority: Minor It is a somewhat common practice for delimited text files such as comma-separated (CSV) or tab delimited files to contain a list of column names in the first line of the file. A sequencer to capture this metadata could be useful,and should be straightforward to implement. -- 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

14 years, 4 months

3
8
0 / 0

[JBoss JIRA] Created: (DNA-64) Sequence JAR files to extract the files and directories

by Randall Hauch (JIRA)

Sequence JAR files to extract the files and directories ------------------------------------------------------- Key: DNA-64 URL: http://jira.jboss.com/jira/browse/DNA-64 Project: DNA Issue Type: Feature Request Components: Sequencers Reporter: Randall Hauch Priority: Minor Fix For: 0.2 The ZIP archive extractor should explode the contents of the archive into the repository. This would enable other sequencers to process the contained files, allowing ZIP files to contain ZIP files. -- 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

14 years, 9 months

2
5
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

14 years, 11 months

4
8
0 / 0

[JBoss JIRA] Created: (DNA-110) write unit test

by Stefano Maestri (JIRA)

write unit test --------------- Key: DNA-110 URL: http://jira.jboss.com/jira/browse/DNA-110 Project: DNA Issue Type: Sub-task Reporter: Stefano Maestri Assigned To: Stefano Maestri -- 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

14 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (DNA-175) ESB message sequencer has a dependency that doesn't exist in the JBoss repository

by Johnny Verhaeg (JIRA)

ESB message sequencer has a dependency that doesn't exist in the JBoss repository --------------------------------------------------------------------------------- Key: DNA-175 URL: http://jira.jboss.com/jira/browse/DNA-175 Project: DNA Issue Type: Bug Reporter: Johnny Verhaeg Assigned To: Stefano Maestri Priority: Critical Fix For: 0.2 The dependency in the pom is to jbossesb-rosetta.jar/jbossesb-rosetta-dep/4.3 -- 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

14 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (DNA-78) Sequence ESB message for governance purposes

by Stefano Maestri (JIRA)

Sequence ESB message for governance purposes -------------------------------------------- Key: DNA-78 URL: http://jira.jboss.com/jira/browse/DNA-78 Project: DNA Issue Type: Feature Request Components: Sequencers Reporter: Stefano Maestri Assigned To: Stefano Maestri Fix For: 0.2 Sequence message from ESB message store can give useful informations from a SOA Governance point of view -- 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

14 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (DNA-58) Create repository configuration and component

by Randall Hauch (JIRA)

Create repository configuration and component --------------------------------------------- Key: DNA-58 URL: http://jira.jboss.com/jira/browse/DNA-58 Project: DNA Issue Type: Task Components: Sequencers Reporter: Randall Hauch Assigned To: Randall Hauch Priority: Critical Fix For: 0.1 There needs to be a configuration object that wraps the sequencing service and makes working with the it easier. -- 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

14 years, 12 months

3
19
0 / 0

[JBoss JIRA] Created: (DNA-101) potential user confusion between org.jboss.dna.spi.graph ValueFactory and ValueFormatException interfaces and similar javax.jcr interfaces

by Greg Haber (JIRA)

potential user confusion between org.jboss.dna.spi.graph ValueFactory and ValueFormatException interfaces and similar javax.jcr interfaces ------------------------------------------------------------------------------------------------------------------------------------------ Key: DNA-101 URL: http://jira.jboss.com/jira/browse/DNA-101 Project: DNA Issue Type: Feature Request Components: API Affects Versions: 0.2 Reporter: Greg Haber Priority: Trivial The new org.jboss.dna.spi.graph.ValueFactory and package org.jboss.dna.spi.graph.ValueFormatException interfaces may be potentially confusing to users that are using both DNA and the underlying JCR APIs in the same code. This is because there are interfaces with exactly the same names, and with very similar purposes (the JCR interfaces deal with instances of the javax.jcr.Value class, where the DNA interfaces are for standard Java objects), in the javax.jcr package. We should think about changing the names of the DNA interfaces to avoid such potential confusion. This is a very minor issue, I would not object if we decided to leave the interface names unchanged. -- 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

15 years

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues July 2008