November 2008 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-219) XML Sequencer should handle decoding names and values containing escape characters

by Johnny Verhaeg (JIRA)

XML Sequencer should handle decoding names and values containing escape characters ---------------------------------------------------------------------------------- Key: DNA-219 URL: https://jira.jboss.org/jira/browse/DNA-219 Project: DNA Issue Type: Bug Components: Sequencers Affects Versions: 0.2 Reporter: Johnny Verhaeg Fix For: 0.3 The XML Sequencer doesn't currently handle names and values that have been encoded to account for illegal characters in an XML document. For example, node names containing spaces, such as "My Documents", will be encoded as "My_x0020_Documents" in the XML file. See JCR spec sections 6.4.3 and 6.4.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

17 years, 5 months

2
1
0 / 0

[JBoss JIRA] Updated: (DNA-48) Development and testing kit for federation connectors

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-48?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-48: ----------------------------- Moved issues from 0.4 to 0.5 during initial planning process for 0.4 release. > Development and testing kit for federation connectors > ----------------------------------------------------- > > Key: DNA-48 > URL: https://jira.jboss.org/jira/browse/DNA-48 > Project: DNA > Issue Type: Feature Request > Components: Connectors, Federation, Testing > Reporter: Randall Hauch > Priority: Minor > Fix For: 0.4 > > > Developing federation connectors will require some documentation and test harnesses that simplifies the task of creating and testing connectors. This should include unit- and integration-level tests, and ways of running these tests as regression tests. Ideally this would also include a way to execute performance tests. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (DNA-31) Sequence XMI models (e.g., UML, MetaMatrix, etc.)

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-31?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-31: ----------------------------- Moved issues from 0.4 to 0.5 during initial planning process for 0.4 release. > Sequence XMI models (e.g., UML, MetaMatrix, etc.) > ------------------------------------------------- > > Key: DNA-31 > URL: https://jira.jboss.org/jira/browse/DNA-31 > Project: DNA > Issue Type: Feature Request > Components: Sequencers > Reporter: Randall Hauch > Assignee: Johnny Verhaeg > Fix For: 0.4 > > > Create a sequencer (or several sequencers) for XMI files, including MetaMatrix and UML models (including ERwin UML export). -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (DNA-32) Sequence XSD files

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-32?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-32: ----------------------------- Moved issues from 0.4 to 0.5 during initial planning process for 0.4 release. > Sequence XSD files > ------------------ > > Key: DNA-32 > URL: https://jira.jboss.org/jira/browse/DNA-32 > Project: DNA > Issue Type: Feature Request > Components: Sequencers > Reporter: Randall Hauch > Fix For: 0.4 > > > Create a sequencer for XML Schema Documents. -- 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, 5 months

1
0
0 / 0

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

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-34?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-34: ----------------------------- Moved issues from 0.4 to 0.5 during initial planning process for 0.4 release. > Federate content stored on file system > -------------------------------------- > > Key: DNA-34 > URL: https://jira.jboss.org/jira/browse/DNA-34 > Project: DNA > Issue Type: Feature Request > Components: Connectors > Reporter: Randall Hauch > Assignee: Stefano Maestri > 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. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (DNA-24) Sequence Maven 2 POM files

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-24?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-24: ----------------------------- Moved issues from 0.4 to 0.5 during initial planning process for 0.4 release. > Sequence Maven 2 POM files > -------------------------- > > Key: DNA-24 > URL: https://jira.jboss.org/jira/browse/DNA-24 > Project: DNA > Issue Type: Feature Request > Components: Sequencers > Reporter: Randall Hauch > Priority: Minor > Fix For: 0.4 > > > Create a sequencer that processes Maven 2 Project Object Model (POM) files and extracts the relevant project metadata (including dependencies). -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (DNA-33) Sequence WSDL files

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-33?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-33: ----------------------------- Moved issues from 0.4 to 0.5 during initial planning process for 0.4 release. > Sequence WSDL files > ------------------- > > Key: DNA-33 > URL: https://jira.jboss.org/jira/browse/DNA-33 > Project: DNA > Issue Type: Feature Request > Components: Sequencers > Reporter: Randall Hauch > Assignee: Stefano Maestri > Fix For: 0.4 > > > Create a sequencer for Web Service Definition Language (WSDL) files. This would be useful for MetaMatrix as well as SOA-P. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (DNA-40) Persistant storage for information not stored in other repository sources

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-40?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-40: ----------------------------- Fix Version/s: 0.4 (was: Future Releases) Affects: [Documentation (Ref Guide, User Guide, etc.), Interactive Demo/Tutorial, Release Notes] Assignee: Randall Hauch Complexity: Medium Priority: Major (was: Minor) Started work on this new connector, which uses Java Persistence Architecture (JPA) to work with EJB3 entities stored in a relational database, using Hibernate for the JPA implementation. (Note that some Hibernate extensions are also used.) The connector is capable of using one of several "models" (or schemas). The initial model is called "Basic", but the connector supports having multiple models (which can be exist in separate packages) and allowing the user to choose via a JavaBean property in the JpaSource object. (Note that the kind of model used in a particular database instance is recorded in the database, and may not be changed. In this case, the JpaSource's model selection is changed to reflect what is in the database. Changing a database's model would require migration, which is not currently supported, but could be provided by a "copy" utility that operates on a graph by generically copying the content from one source to another.) Each model is also responsible for creating the RequestProcessor implementation, so the JpaSource and JpaConnection implementations can work with any model. The "Basic" model stores for each node a single record containing the node ID (which is a UUID string) and a blob for the serialized properties. Large property values (of type 'string' or 'binary') are not included in the serialized properties, but are instead stored separately in a table that stores the value (as a blob) keyed by the SHA-1 hash of the value. This means that if multiple "large" properties (on the same or multiple nodes) have the exact same value, that property value will be stored only once in the database. Also, each parent-child relationship is also stored as a separate record, allowing direct manipulation of the database when finding, creating, or moving children (including adjusting the same-name-sibling indexes). Each of these child entities has the local name of the node, a reference to the namespace in which the node's name exists, the same-name-sibling index, and the index in the parent list of children. All namespaces are centralized in a single table so they can be reused. The current implementation is probably close to 75% complete. The "Basic" entities are mostly completed (minor changes are anticipated), and all of the source infrastructure has been completed. Most of the outstanding work is in the BasicRequestProcessor implementation. > Persistant storage for information not stored in other repository sources > ------------------------------------------------------------------------- > > Key: DNA-40 > URL: https://jira.jboss.org/jira/browse/DNA-40 > Project: DNA > Issue Type: Feature Request > Components: Connectors > Reporter: Randall Hauch > Assignee: Randall Hauch > Fix For: 0.4 > > > Create a federation connector that is able to manage information in a relational database using a DNA-defined schema. This would enable the persistant storage of information that isn't being managed by other connectors. > Requirements include efficiently storing and accessing large numbers of nodes, large property values (e.g., Binary values), and large numbers of children on nodes. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (DNA-231) org.jboss.dna.graph.xml.XmlSequencerTest failed with jdk 1.6 (not with jdk 1.5)

by Serge Emmanuel Pagop (JIRA)

org.jboss.dna.graph.xml.XmlSequencerTest failed with jdk 1.6 (not with jdk 1.5) ------------------------------------------------------------------------------- Key: DNA-231 URL: https://jira.jboss.org/jira/browse/DNA-231 Project: DNA Issue Type: Bug Components: SPI Affects Versions: 0.3 Environment: Testing on Mac OS x 10.5 with Java(TM) SE Runtime Environment (build 1.6.0_05-b13-120) Reporter: Serge Emmanuel Pagop Assignee: Randall Hauch Priority: Minor Fix For: 0.3 maybe a jdk 1.5 bug, because of the decode of the entity > - the output with with jdk 1.5 expected: "/a/b/c@title => /d/e/f" actual: "/a/b/c@title => /d/e/f" - the output with with jdk 1.6 ( the specific entity ">" is replaced with the corresponding character ">") expected: "/a/b/c@title => /d/e/f" actual: "/a/b/c@title = > /d/e/f" --- Error trace ------------------------------------------------------------------------------- Test set: org.jboss.dna.graph.xml.XmlSequencerTest ------------------------------------------------------------------------------- Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.147 sec <<< FAILURE! shouldSequenceElementContent(org.jboss.dna.graph.xml.XmlSequencerTest) Time elapsed: 0.506 sec <<< FAILURE! java.lang.AssertionError: Expected: is "/a/b/c@title => /d/e/f" got: "/a/b/c@title = > /d/e/f" at org.junit.Assert.assertThat(Assert.java:502) at org.junit.Assert.assertThat(Assert.java:492) at org.jboss.dna.graph.xml.XmlSequencerTest.verifyString(XmlSequencerTest.java:225) at org.jboss.dna.graph.xml.XmlSequencerTest.shouldSequenceElementContent(XmlSequencerTest.java:155) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59) at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98) at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79) at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87) at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77) at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42) at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88) at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51) at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37) at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997) -- 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, 5 months

5
7
0 / 0

[JBoss JIRA] Updated: (DNA-55) REST-based API for remote access and usage

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-55?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-55: ----------------------------- Fix Version/s: 0.4 (was: Future Releases) Priority: Major (was: Minor) I thought this post about enunciate (http://enunciate.codehaus.org/) was interesting, considering the recent discussion about a RESTful API for DNA: http://blogs.citytechinc.com/sjohnson/?p=30 > REST-based API for remote access and usage > ------------------------------------------ > > Key: DNA-55 > URL: https://jira.jboss.org/jira/browse/DNA-55 > Project: DNA > Issue Type: Feature Request > Components: Server, Web Application > Reporter: Randall Hauch > Fix For: 0.4 > > > Create a DNA server that uses a REST-based API, allowing client applications to access and use the repository using HTTP for protocol/transport. > AtomPub is also very interesting (as it is RESTful) for a message structure, but it doesn't currently support hierarchical data. And although one could build a repository to be flatter (or at least exposed though collections; see how Bento does it: http://www.filemaker.com/bento/), it may be difficult to have no way of interacting with the hierarchical data. Bento and iTunes both show how powerful user-defined collections (and "smart collections") can be, so maybe adopting a collection-only approach would work (at least for remote access). -- 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, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues November 2008