April 2009 - dna-issues - Jboss List Archives

[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

15 years

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

15 years

2
5
0 / 0

[JBoss JIRA] Created: (DNA-388) AbstractJcrNode.getReferences() is incorrectly implemented

by Randall Hauch (JIRA)

AbstractJcrNode.getReferences() is incorrectly implemented ---------------------------------------------------------- Key: DNA-388 URL: https://jira.jboss.org/jira/browse/DNA-388 Project: DNA Issue Type: Bug Components: JCR Reporter: Randall Hauch Fix For: 0.5 The getReferences() call is not implemented according to spec. -- 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
3
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

15 years

2
2
0 / 0

[JBoss JIRA] Created: (DNA-385) Documentation Updates for 0.4

by Brian Carothers (JIRA)

Documentation Updates for 0.4 ----------------------------- Key: DNA-385 URL: https://jira.jboss.org/jira/browse/DNA-385 Project: DNA Issue Type: Bug Components: Documentation Affects Versions: 0.3 Reporter: Brian Carothers Fix For: 0.4 We need to update all of the documentation to reflect the changes made for 0.4. -- 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-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-378) XML Graph Importer should support importing multi-valued properties

by Randall Hauch (JIRA)

XML Graph Importer should support importing multi-valued properties -------------------------------------------------------------------- Key: DNA-378 URL: https://jira.jboss.org/jira/browse/DNA-378 Project: DNA Issue Type: Feature Request Components: API, Graph Reporter: Randall Hauch Fix For: 0.4 The XML handler used in the Graph importer (that is, org.jboss.dna.graph.xml.XmlHandler) does not currently support producing multi-valued properties. This is a fairly substantial limitation. The current XML handler simply maps an XML element to a graph node and an XML attribute to a property. There is no such thing as multi-valued XML attributes, so another mapping has to be used for multi-valued properties. Since a graph node does not directly hold any values (rather, it holds properties that have the values), and the XML handler currently ignores all XML character content (e.g., <element>this is character content</element>), it is fairly logical to conclude that a child XML element with character content should be mapped to a property. If there is a "jcr:name" attribute, then this attribute's value would be used to determine the property name (meaning the element's name could be anything); otherwise, the child element's name would be the property name. This would also address the shortcoming of XML attribute values not being able to (easily) have any character content, since such property values could be placed in a child element. Here's an example: <cars> <car jcr:name="Mini"> <jcr:description>This is a description that would be stored as a property on the 'Mini' node</jcr:description> <property jcr:name="summary">This is the value of the 'summary' property on the 'Mini' node</property> </car> </cars> I'm not sure how easy it is to change the XmlHandler to behave this way, since under certain situations it may require postponing the creation of a node since it is unknown when processing a "startElement" method that the element has character content. However, I believe that it is worth any additional complexity to make the XML more intuitive and natural. -- 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
10
0 / 0

[JBoss JIRA] Created: (DNA-387) Federation connector does not support updates, which are required when using with the JCR implementation

by Randall Hauch (JIRA)

Federation connector does not support updates, which are required when using with the JCR implementation -------------------------------------------------------------------------------------------------------- Key: DNA-387 URL: https://jira.jboss.org/jira/browse/DNA-387 Project: DNA Issue Type: Bug Components: Connectors, Examples Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Blocker Fix For: 0.4 Our JCR implementation updates the "/jcr:system/dna:namespaces" and "/jcr:system/nodeTypes" areas as the namespaces and node types change, respectively. The federation connector doesn't support updates, and using the federation connector with our JCR results in errors running the repository examples for the Getting Started guide. These updates follow a specific and limited pattern: all of the updates are within a single projection, and in these cases the update requests can be transformed and sent down to the one connector for the projection. This very limited scenario would go a long way, and its pretty straightforward. -- 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
2
0 / 0

[JBoss JIRA] Created: (DNA-386) AbstractJcrNode Javadoc Throws Clause Are Out Of Sync

by Brian Carothers (JIRA)

AbstractJcrNode Javadoc Throws Clause Are Out Of Sync ----------------------------------------------------- Key: DNA-386 URL: https://jira.jboss.org/jira/browse/DNA-386 Project: DNA Issue Type: Bug Components: Documentation, JCR Affects Versions: 0.3 Reporter: Brian Carothers Priority: Optional Fix For: 0.4 Some of the methods in AbstractJcrNode still have Javadoc for the UnsupportedOperationException that they used to throw. According to a quick text search of all the places where "@throws Unsupported" occurs in dna-jcr, this is the only file with this type of erroneous Javadoc. I also marked off the getReferences method as it is not implemented per spec. -- 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
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues April 2009