[jira] [Commented] (OAK-41) Initial repository setup
[ https://issues.apache.org/jira/browse/OAK-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13467565#comment-13467565 ] angela commented on OAK-41: --- please note that - initial users - initial permissions are depending on the configured setup and implementation. we cannot assume that users or permissions are stored in one particular way. the same applies for those parts of :unique constraint that are bound to a particular implementation (i added a FIXME there). Initial repository setup Key: OAK-41 URL: https://issues.apache.org/jira/browse/OAK-41 Project: Jackrabbit Oak Issue Type: Task Components: core Reporter: angela Attachments: OAK-41-initial-proposal.patch upon the initial creation of a JCR repository the associated SPI layer (oak-core) should take care of setting up the corresponding MK-instance. this includes (incomplete list): - create the jcr repo (not sure what that means in terms of mk-implementation) - create the jcr:system node (unique for the repository, across workspaces) - create the default workspace (- name from config) - create the root node of the default workspace in addition the repository would need to have access to the following information (maybe also mk-nodes underneath jcr:system ??) - built-in node types - built-in namespace - built-in privileges - built-in permissions - repository configuration (can that be stored in the mk?) as far as the workspace is concerned a functional repository would in addition need to have: - build-in users (based on some sort of configuration) - workspace configuration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OAK-354) Support node types and node type inheritance in query
angela created OAK-354: -- Summary: Support node types and node type inheritance in query Key: OAK-354 URL: https://issues.apache.org/jira/browse/OAK-354 Project: Jackrabbit Oak Issue Type: Sub-task Components: core Reporter: angela i recently tried to run some user mgt related test and found that they might be failing due to a query that restricts the results to nodes of a particular base node type. adding this sub-task as a reminder and to be able to cover dependencies here in jira -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OAK-269) Query: IndexManager to manage existing indexes
[ https://issues.apache.org/jira/browse/OAK-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu resolved OAK-269. - Resolution: Invalid dropped the idea Query: IndexManager to manage existing indexes -- Key: OAK-269 URL: https://issues.apache.org/jira/browse/OAK-269 Project: Jackrabbit Oak Issue Type: Bug Components: core Reporter: Alex Parvulescu Assignee: Alex Parvulescu We need a new component in oak-core that will allow easier management of existing indexes. It sould rely on a config node for index creation at initialisation time, as well as observation to pick up on config changes at runtime. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OAK-237) Run Jackrabbit query tests
[ https://issues.apache.org/jira/browse/OAK-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated OAK-237: -- Attachment: 0001-OAK-237-Run-Jackrabbit-query-tests.patch Attached an updated version of the test patch. Run Jackrabbit query tests -- Key: OAK-237 URL: https://issues.apache.org/jira/browse/OAK-237 Project: Jackrabbit Oak Issue Type: Improvement Components: jcr Reporter: Alex Parvulescu Assignee: Alex Parvulescu Attachments: 0001-OAK-237-Run-Jackrabbit-query-tests.patch, OAK-237-full-trace.log.zip, OAK-237.patch, OAK-237-v2.patch Following JCR-3408 we are now able to run most of the queries from jackrabbit-core in oak-jcr. I think this will help with query parsing as well as verifying where we stand in terms of the new query engine compared to jr. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OAK-91) Implement Authentication Support
[
https://issues.apache.org/jira/browse/OAK-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13467875#comment-13467875
]
Jukka Zitting commented on OAK-91:
--
Plugging in _non-JAAS_ authentication components was a bit complicated since
the JAAS {{LoginContext}} is not an interface but a class whose constructor
does some pretty tricky classloading magic that's hard to override when it's
not needed.
To solve this issue, in revision 1393038 I replaced the {{LoginContext}} return
value of the {{LoginContextProvider.getLoginContext()}} method with a new
{{OakLoginContext}} interface that simply duplicates all the methods of the
JAAS {{LoginContext}} class. A related {{JaasLoginContext}} class simply
implements this new interface using the JAAS {{LoginContext}} as a base class,
which keeps full compatibility with existing JAAS-based authentication
components.
Implement Authentication Support
Key: OAK-91
URL: https://issues.apache.org/jira/browse/OAK-91
Project: Jackrabbit Oak
Issue Type: Task
Components: core, jcr
Reporter: angela
Assignee: angela
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
