May 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-441) JcrWorkspace.move and .clone Don't Check Node Type Constraints or Permissions

by Brian Carothers (JIRA)

JcrWorkspace.move and .clone Don't Check Node Type Constraints or Permissions ----------------------------------------------------------------------------- Key: DNA-441 URL: https://jira.jboss.org/jira/browse/DNA-441 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.4 Reporter: Brian Carothers Fix For: 0.5 The workspace move and copy operations are missing some of the required checks, impacting the JR TCK nightly 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

15 years

2
4
0 / 0

[JBoss JIRA] Created: (DNA-439) JcrNode.setProperty(String, String|Value, int) Doe sNot Always Throw ConstraintViolationException Correctly

by Brian Carothers (JIRA)

JcrNode.setProperty(String, String|Value, int) Doe sNot Always Throw ConstraintViolationException Correctly ----------------------------------------------------------------------------------------------------------- Key: DNA-439 URL: https://jira.jboss.org/jira/browse/DNA-439 Project: DNA Issue Type: Bug Affects Versions: 0.4 Reporter: Brian Carothers Assignee: Brian Carothers Priority: Minor Fix For: 0.5 The JR TCK test SetPropertyAssumeTypeTest has two test cases for Node.setProperty(String, String|Value, int) with invalid types. Both are currently failing. -- 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-316) Get DNA running in a web app and used by JAX-RS classes

by Johnny Verhaeg (JIRA)

Get DNA running in a web app and used by JAX-RS classes ------------------------------------------------------- Key: DNA-316 URL: https://jira.jboss.org/jira/browse/DNA-316 Project: DNA Issue Type: Sub-task Components: Web Application Affects Versions: 0.3 Reporter: Johnny Verhaeg We still have to determine what presentation technology to start with (GWT, Flex, JavaFX, Seam, etc.) -- 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

3
3
0 / 0

[JBoss JIRA] Created: (DNA-315) Implement HTTP DELETE action for any resource at any path (folder or file)

by Johnny Verhaeg (JIRA)

Implement HTTP DELETE action for any resource at any path (folder or file) -------------------------------------------------------------------------- Key: DNA-315 URL: https://jira.jboss.org/jira/browse/DNA-315 Project: DNA Issue Type: Sub-task Components: Web Application Affects Versions: 0.3 Reporter: Johnny Verhaeg Provides basic un-publish capability -- 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

3
3
0 / 0

[JBoss JIRA] Created: (DNA-314) Implement HTTP POST action for any resource at any path (folder or file)

by Johnny Verhaeg (JIRA)

Implement HTTP POST action for any resource at any path (folder or file) ------------------------------------------------------------------------ Key: DNA-314 URL: https://jira.jboss.org/jira/browse/DNA-314 Project: DNA Issue Type: Sub-task Components: Web Application Affects Versions: 0.3 Reporter: Johnny Verhaeg Not sure yet what this action would do other than duplicate a PUT -- 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

3
3
0 / 0

[JBoss JIRA] Created: (DNA-313) Implement HTTP PUT action for any resource at any path (folder or file)

by Johnny Verhaeg (JIRA)

Implement HTTP PUT action for any resource at any path (folder or file) ----------------------------------------------------------------------- Key: DNA-313 URL: https://jira.jboss.org/jira/browse/DNA-313 Project: DNA Issue Type: Sub-task Components: Web Application Affects Versions: 0.3 Reporter: Johnny Verhaeg Provides basic publish capability -- 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

3
3
0 / 0

[JBoss JIRA] Created: (DNA-309) Design URLs, leaving room for future UI features and maybe WebDAV

by Johnny Verhaeg (JIRA)

Design URLs, leaving room for future UI features and maybe WebDAV ----------------------------------------------------------------- Key: DNA-309 URL: https://jira.jboss.org/jira/browse/DNA-309 Project: DNA Issue Type: Sub-task Components: Web Application Affects Versions: 0.3 Reporter: Johnny Verhaeg For right now, we need URLs for just publishing and un-publishing content. -- 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

3
20
0 / 0

[JBoss JIRA] Created: (DNA-312) Implement HTTP GET action for any resource at any path (folder or file)

by Johnny Verhaeg (JIRA)

Implement HTTP GET action for any resource at any path (folder or file) ----------------------------------------------------------------------- Key: DNA-312 URL: https://jira.jboss.org/jira/browse/DNA-312 Project: DNA Issue Type: Sub-task Components: Web Application Affects Versions: 0.3 Reporter: Johnny Verhaeg This provides basic read capability of the artifacts published to the repository -- 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

3
6
0 / 0

[JBoss JIRA] Created: (DNA-438) JR TCK Test SetValueValueFormatExceptionTest Fails

by Brian Carothers (JIRA)

JR TCK Test SetValueValueFormatExceptionTest Fails -------------------------------------------------- Key: DNA-438 URL: https://jira.jboss.org/jira/browse/DNA-438 Project: DNA Issue Type: Bug Affects Versions: 0.4 Reporter: Brian Carothers Priority: Minor Fix For: 0.5 All test cases in this test currently fail. The expected behavior (in general) seems to be that Property.setValue(T value) requires that the value be convertible to the current type of the property, even if the property has a definition that would allow the value in its "native type". -- 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-403) Federation connector does not behave properly in many situations

by Randall Hauch (JIRA)

Federation connector does not behave properly in many situations ---------------------------------------------------------------- Key: DNA-403 URL: https://jira.jboss.org/jira/browse/DNA-403 Project: DNA Issue Type: Bug Components: Connectors, Federation Affects Versions: 0.4 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Blocker Fix For: 0.5 The federation connector is not well behaved when it comes to a number of very common situations. In particular, there seem to be a lot of failures when attempting to repeatedly find nodes by UUID. I suspect that the cache layer is not being updated correctly. There are also several issues with the fundamental design. Currently, all operations against the cache and any sources are performed serially, despite the fact that each connector's processing of requests submitted to it is complete independent of all other connectors. This means that all source connector processing could be parallelized. Another issue is that when a CompositeRequest is submitted to the federation connector, these requests are treated as if they are being done within a single (logical) transaction. However, often times the processing of a request submitted to the federated connector results in one or more requests being made to the source connectors, and these source requests are submitted individually (rather than in a single CompositeRequest corresponding to that submitted to the federated connector). Thus, there is no tie between the source connections and federated connection. Although we don't supported distributed transactions, this certainly doesn't come close to helping align the logical transactions of each connector. Third, the federation connector does not optimize for some common situations, such as a single mirror projection (e.g., "/ => /", where the federation connector is really just mirroring another source), an offset projection (e.g., "/ => /a/b" or "/c/d => /", where the federation connector is mirroring a subset of another connector or prepends a leading path), a mirror-with-branch case (e.g., "/ => /" for source A, and "/jcr:system => /jcr:system" for source B). The latter condition is likely to be used in the JCR implementation to project a single "/jcr:system" branch (which will exist in its own workspace in a JCR repository) into each normal JCR workspace. Finally, as just mentioned, the federation connector has the potential to be used in a number of situations within other non-extension projects (e.g., "dna-jcr"). This is not really feasible with the current connector, since it is a normal extension and not a first-class feature of the 'dna-graph'. Therefore, the federation connector should be moved into 'dna-graph' similar to the In-Memory connector. -- 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
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues May 2009