March 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Updated: (DNA-55) Web Application with 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: ----------------------------- Summary: Web Application with REST-based API for remote access and usage (was: REST-based API for remote access and usage) > Web Application with 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.5 > > > 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

15 years, 1 month

1
0
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.5 (was: 0.4) Changed the target release from 0.4 to 0.5 to reflect current roadmap. We should definitely look at using RESTeasy, since that's a JAX-RS implementation that makes it pretty easy to make something that can deploy to a number of web/app servers. > 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.5 > > > 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Deleted: (DNA-307) Build process needs to allow for DNA to be deployable within a container such as JBoss AS/EAP

by Johnny Verhaeg (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-307?page=com.atlassian.jira.plugin... ] Johnny Verhaeg deleted DNA-307: ------------------------------- > Build process needs to allow for DNA to be deployable within a container such as JBoss AS/EAP > --------------------------------------------------------------------------------------------- > > Key: DNA-307 > URL: https://jira.jboss.org/jira/browse/DNA-307 > Project: DNA > Issue Type: Feature Request > Reporter: Johnny Verhaeg > > DNA should be built such that it can be deployed in and made available to other applications (e.g, JBoss Tools, Teiid Designer, etc.) via a container such as JBoss AS/ESP. The Maven build process would need to produce a WAR file, and we need to determine how configuration affects this. -- 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 month

1
0
0 / 0

[JBoss JIRA] Created: (DNA-307) Build process needs to allow for DNA to be deployable within a container such as JBoss AS/EAP

by Johnny Verhaeg (JIRA)

Build process needs to allow for DNA to be deployable within a container such as JBoss AS/EAP --------------------------------------------------------------------------------------------- Key: DNA-307 URL: https://jira.jboss.org/jira/browse/DNA-307 Project: DNA Issue Type: Feature Request Components: Server Affects Versions: 0.3 Reporter: Johnny Verhaeg DNA should be built such that it can be deployed in and made available to other applications (e.g, JBoss Tools, Teiid Designer, etc.) via a container such as JBoss AS/ESP. The Maven build process would need to produce a WAR file, and we need to determine how configuration affects this. -- 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 month

1
0
0 / 0

[JBoss JIRA] Created: (DNA-304) SessionCache Uses Graph Layer Cardinality for Properties Instead of Cardinality from JCR Property Definition

by Brian Carothers (JIRA)

SessionCache Uses Graph Layer Cardinality for Properties Instead of Cardinality from JCR Property Definition ------------------------------------------------------------------------------------------------------------ Key: DNA-304 URL: https://jira.jboss.org/jira/browse/DNA-304 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.4 Reporter: Brian Carothers At the graph layer, property cardinality (whether the property is single- or multi-valued) is determined based on the values set on the property (i.e., any property with only one value is single-valued, any property with more than one value is multi-valued). At the JCR layer, property cardinality is supposed to be based on the property definition in use for the property. The SessionCache is currently basing the JCR layer cardinality on the graph layer cardinality instead of the JCR property definition. Example: Consider a node that has one value for jcr:mixinTypes. At the graph layer, this property will be single-valued. At the JCR layer, this property should be multi-valued based on the jcr:mixinTypes property definition from the nt:base type (which is inherited by all 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

15 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (DNA-297) JcrSession.exportDocumentView Does Not Export Carriage Returns, Line Feeds, and Tabs Correctly

by Brian Carothers (JIRA)

JcrSession.exportDocumentView Does Not Export Carriage Returns, Line Feeds, and Tabs Correctly ---------------------------------------------------------------------------------------------- Key: DNA-297 URL: https://jira.jboss.org/jira/browse/DNA-297 Project: DNA Issue Type: Bug Affects Versions: 0.4 Reporter: Brian Carothers Priority: Minor JcrSession.exportDocumentView did not properly encode carriage returns, line feeds, or tabs during export as described in section 6.4.4 of the 1.0.1 specification. -- 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 month

2
5
0 / 0

[JBoss JIRA] Created: (DNA-300) The DNA PathNotFoundException message text does not include the lowest existing path that was found

by Randall Hauch (JIRA)

The DNA PathNotFoundException message text does not include the lowest existing path that was found --------------------------------------------------------------------------------------------------- Key: DNA-300 URL: https://jira.jboss.org/jira/browse/DNA-300 Project: DNA Issue Type: Bug Components: API, Graph Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Minor Fix For: 0.4 The PathNotFoundException that is part of the DNA Graph API has the lowest existing path that was found along the requested path. This path, however, is only available as a field on the exception, and does not show up in the exception message, either through getMessage() or getLocalizedMessage(). The message should include the lowest existing path, and should be internationalized using GraphI18n. -- 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 month

1
2
0 / 0

[JBoss JIRA] Created: (DNA-299) Path.isNormalized() is incorrect if the path begins with parent reference(s)

by Randall Hauch (JIRA)

Path.isNormalized() is incorrect if the path begins with parent reference(s) ---------------------------------------------------------------------------- Key: DNA-299 URL: https://jira.jboss.org/jira/browse/DNA-299 Project: DNA Issue Type: Bug Components: API, Graph Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.4 The different implementations of Path consider a path that begins with a one or more parent references as not normalized. For example, "../a" should be considered normalized, but it is not. Normalized means that there are no self-reference segments (e.g., "."), and that all parent references that can be removed are removed. Therefore, "../a" should be normalized, whereas "/../a" is not normalized. There were no unit tests that covered these conditions. -- 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 month

1
2
0 / 0

[JBoss JIRA] Created: (DNA-298) SVNRepositoryTest Fails on Windows

by Brian Carothers (JIRA)

SVNRepositoryTest Fails on Windows ---------------------------------- Key: DNA-298 URL: https://jira.jboss.org/jira/browse/DNA-298 Project: DNA Issue Type: Bug Components: Connectors Affects Versions: 0.4 Environment: JDK 1.6.0_012, Windows XP Reporter: Brian Carothers Priority: Minor Two tests in SVNRepositoryTest fail when running on Windows. The tests are: shouldCreateFSRepositoryIfProtocolIsOfTypeFile shouldAllowMultipleConnectionsToBeOpenAtTheSameTime Both fail with (essentially) the same stack trace: org.jboss.dna.graph.connector.RepositorySourceException: Protocol is not supported by this connector or there is problem in the svn url at org.jboss.dna.connector.svn.SVNRepositorySource.getConnection(SVNRepositorySource.java:300) at org.jboss.dna.connector.svn.SVNRepositorySourceTest.shouldCreateFSRepositoryIfProtocolIsOfTypeFile(SVNRepositorySourceTest.java:240) 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.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) -- 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 month

2
3
0 / 0

[JBoss JIRA] Created: (DNA-296) JcrSession Sometimes Eschews Single-Valued Variants of PropertyDefinitions

by Brian Carothers (JIRA)

JcrSession Sometimes Eschews Single-Valued Variants of PropertyDefinitions -------------------------------------------------------------------------- Key: DNA-296 URL: https://jira.jboss.org/jira/browse/DNA-296 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.4 Reporter: Brian Carothers JcrSession.populateNode infers the property definition for each property by doing a property lookup by name and, if that fails, by checking for a matching residual property definition. This lookup also needs to compare by cardinality (single-valued vs. multi-valued). Correcting this obviates the need for dna:xmlText and dna:xmlContent from the DNA-295 defect. -- 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 month

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues March 2009