February 2009 - dna-issues - Jboss List Archives

[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

14 years, 11 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

14 years, 11 months

4
8
0 / 0

[JBoss JIRA] Created: (DNA-190) Support accessing repository through WebDAV

by Randall Hauch (JIRA)

Support accessing repository through WebDAV ------------------------------------------- Key: DNA-190 URL: https://jira.jboss.org/jira/browse/DNA-190 Project: DNA Issue Type: Feature Request Components: API, Server Reporter: Randall Hauch Fix For: 0.3 The Guvnor project is now using WebDAV to access JCR repositories. (See attached PDF.) Therefore, to enable Guvnor to use DNA, we need to support WebDAV access, which means we'll need a web application that can be deployed to an app server (or web server). -- 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

14 years, 11 months

2
4
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, 12 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, 12 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, 12 months

2
5
0 / 0

[JBoss JIRA] Created: (DNA-218) Implement a Sequencer for Spring bean configuration files

by Ben Abernathy (JIRA)

Implement a Sequencer for Spring bean configuration files ---------------------------------------------------------- Key: DNA-218 URL: https://jira.jboss.org/jira/browse/DNA-218 Project: DNA Issue Type: Feature Request Components: Sequencers Reporter: Ben Abernathy Priority: Optional Fix For: 0.3 Implement a sequencer that can parse Spring 2.5.x bean configuration XML files and store information about each bean. In particular, look at storing information the bean's name and possibly its attributes including relationships with other defined beans (through refs). I haven't had a chance to identify any of the specific artifacts yet (documentation, demo, etc). I will create subtasks as necessary. -- 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

14 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (DNA-277) Fix all text files in source code to have consistent line feeds

by Randall Hauch (JIRA)

Fix all text files in source code to have consistent line feeds --------------------------------------------------------------- Key: DNA-277 URL: https://jira.jboss.org/jira/browse/DNA-277 Project: DNA Issue Type: Task Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Johnny Verhaeg Priority: Minor Fix For: 0.4 Currently, all of the text files in our source code have a mixture of carriage returns and line feeds. And, our DNA preferences (for Eclipse) did not specify any special handling, so each developer's settings were used (and likely were the default settings for the platform). Regardless of the preference settings, however, Eclipse editors always keep the line termination characters used in each particular file, so if a file was created on Windows, it will have \r\n for all lines, even when that file is modified on Linux or OS X. There are a few cases where a file seems to have a mixture of line terminations. We should probably have a consistent line terminator in all files, and that terminator should probably be '\n', which is the line terminator on *nix, for a couple of reasons. First, the JBoss.org SVN repository is hosted on Linux, and being consistent probably helps somewhat. Second, some tools (including Git) rely upon the '\n' character for determining line feeds, so that rules out the Mac style line feeds ('\r'). Third, there really is no need to store multiple characters. We need to verify that the converting all files to use Unix line terminators is acceptable. If so, we need to convert all of the files (that need it), update the Eclipse preferences, and have all developers make sure their Eclipse preference settings are correct. -- 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
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

15 years

3
19
0 / 0

[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

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues February 2009