May 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-392) All sessions in a repository should share the same /jcr:system content

by Randall Hauch (JIRA)

All sessions in a repository should share the same /jcr:system content ---------------------------------------------------------------------- Key: DNA-392 URL: https://jira.jboss.org/jira/browse/DNA-392 Project: DNA Issue Type: Task Reporter: Randall Hauch Assignee: Randall Hauch Currently each JcrSession has its own copy of the /jcr:system content branch. Technically this is incorrect, since all of the information in this branch is common to and shared by all sessions/workspaces in the repository. One approach to making this work is to have a special workspace in the repository in which the content from the "/jcr:system" branch is placed, and have this workspace projected into each session. -- 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

16 years, 8 months

1
9
0 / 0

[JBoss JIRA] Created: (DNA-399) Need to Add Session.checkPermission Calls to Guard Read, Add Node, Set Property, and Remove Item Access

by Brian Carothers (JIRA)

Need to Add Session.checkPermission Calls to Guard Read, Add Node, Set Property, and Remove Item Access ------------------------------------------------------------------------------------------------------- Key: DNA-399 URL: https://jira.jboss.org/jira/browse/DNA-399 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.4 Reporter: Brian Carothers Fix For: 0.5 Now that JcrSession.checkPermission works (assuming patch takes), we need to add checkPermission calls to guard "read", "add_node", "remove", and "set_property" access, as 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

16 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (DNA-389) Change Getting Started examples to use the DnaConfiguration and JcrConfiguration components

by Randall Hauch (JIRA)

Change Getting Started examples to use the DnaConfiguration and JcrConfiguration components ------------------------------------------------------------------------------------------- Key: DNA-389 URL: https://jira.jboss.org/jira/browse/DNA-389 Project: DNA Issue Type: Task Components: Documentation, Examples Reporter: Randall Hauch Fix For: 0.5 The DnaConfiguration and JcrConfiguration components were created previously (see DNA-58), but the Getting Started examples and document (and Reference Guide document) need to be changed to use them. -- 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

16 years, 10 months

1
6
0 / 0

[JBoss JIRA] Created: (DNA-415) Remove JSR-92 and the 'org.jboss.dna.repository.rules' package

by Randall Hauch (JIRA)

Remove JSR-92 and the 'org.jboss.dna.repository.rules' package -------------------------------------------------------------- Key: DNA-415 URL: https://jira.jboss.org/jira/browse/DNA-415 Project: DNA Issue Type: Task Components: Sequencers Affects Versions: 0.4 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.5 The 'org.jboss.dna.repository.rules' package is still not used by the sequencing service (nor are there plans to use it), so it should be removed. It can always be resurrected from old releases (or from history). -- 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

16 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (DNA-318) Provide documentation/examples/tutorial explaining use of RESTful API

by Johnny Verhaeg (JIRA)

Provide documentation/examples/tutorial explaining use of RESTful API --------------------------------------------------------------------- Key: DNA-318 URL: https://jira.jboss.org/jira/browse/DNA-318 Project: DNA Issue Type: Sub-task Components: Documentation, Web Application Affects Versions: 0.3 Reporter: Johnny Verhaeg -- 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

16 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (DNA-405) Update the Getting Started doc and examples with the new configuration and to remove dependency on Jackrabbit

by Randall Hauch (JIRA)

Update the Getting Started doc and examples with the new configuration and to remove dependency on Jackrabbit ------------------------------------------------------------------------------------------------------------- Key: DNA-405 URL: https://jira.jboss.org/jira/browse/DNA-405 Project: DNA Issue Type: Task Components: Connectors, Documentation, Examples, Sequencers Affects Versions: 0.4 Reporter: Randall Hauch Priority: Critical Fix For: 0.5 Per changes to the configuration, ObservationService (DNA-404), and SequencingService (DNA-401), we need to update the Getting Started doc and examples to use the new configuration mechanism and to remove dependency on Jackrabbit. -- 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

16 years, 10 months

1
6
0 / 0

[JBoss JIRA] Created: (DNA-440) Integrate Servlet Security with DNA ExecutionContext

by Brian Carothers (JIRA)

Integrate Servlet Security with DNA ExecutionContext ---------------------------------------------------- Key: DNA-440 URL: https://jira.jboss.org/jira/browse/DNA-440 Project: DNA Issue Type: Sub-task Affects Versions: 0.4 Reporter: Brian Carothers Fix For: 0.6 The DNA JCR security approach is JAAS-based and relies on the ability to pass a LoginContext, AccessControlContext, or SimpleCredentials (which are used internally to create a LoginContext) to the ExecutionContext. The Servlet specification does not expose any of these. The REST server is mandatorily limited to what the Servlet specification provides. There needs to be some sort of integration between the Servlet-based REST code and JAAS-based DNA implementation to allow authorization and access to JCR resources to occur based on web credentials. -- 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

16 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (DNA-436) Repository example uses different path in configuration repository than assumed by RepositoryService

by Randall Hauch (JIRA)

Repository example uses different path in configuration repository than assumed by RepositoryService ---------------------------------------------------------------------------------------------------- Key: DNA-436 URL: https://jira.jboss.org/jira/browse/DNA-436 Project: DNA Issue Type: Bug Components: Documentation, Examples Affects Versions: 0.4 Reporter: Randall Hauch Priority: Minor Fix For: 0.5 The RepositoryService looks for the configuration information in the repository source (supplied by name via the constructor) by default under the "/jcr:system" path. However, the repository example has a configRepository.xml file in which the content is stored under the "/dna:system" path. Although it's possible to use the RepositoryService constructor and specify the correct path, the examples should be such that the path used in the examples is that assumed by the RepositoryService. Therefore, we should change the repository example configuration file to reflect the current default used by the RepositoryService. -- 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

16 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (DNA-376) Add request to change the order of a child node (or nodes) relative to the other children

by Randall Hauch (JIRA)

Add request to change the order of a child node (or nodes) relative to the other children ----------------------------------------------------------------------------------------- Key: DNA-376 URL: https://jira.jboss.org/jira/browse/DNA-376 Project: DNA Issue Type: Feature Request Components: API, Graph Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Critical Fix For: 0.4 The current DNA Graph model does support ordered children, and while rename can be used to change the order of same-name-siblings, there currently is no way to change the order of the child nodes. This is required to fully implement the JCR API. JCR handles this functionality by provided a method that essentially changes the position of a single child node. The "Node.orderBefore(String childNameToBeMoved, String nameOfChildAtPosition)" can be used by calling on the parent node and supplying the name (with SNS index if needed) of the child to be moved and the name of the child before which the other child is to be moved. This same model can be used for the graph request. It also would allow adding in the future another optional request that would contain multiple reorders, and that could be implemented in RequestProcessor to break into multiple ReorderChildRequest instances. The existing (writable) connectors will all be affected, since this will be a new mandatory request. -- 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

16 years, 10 months

2
8
0 / 0

[JBoss JIRA] Created: (DNA-437) TCK Tests Fail on Workspace.copy

by Brian Carothers (JIRA)

TCK Tests Fail on Workspace.copy -------------------------------- Key: DNA-437 URL: https://jira.jboss.org/jira/browse/DNA-437 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.4 Reporter: Brian Carothers Several of the TCK tests for Workspace.copy 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

16 years, 10 months

1
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues May 2009