This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • Sling-based JCR explorer
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Here's a quick and dirty spec for a JCR Explorer, feel free to expand/refine!

Requirements

More or less in priority order:

Visualize the nodes of the JCR repository in a tree view, and/or in a search view with a search box at the top and a list of matching Nodes below.

Display all the details of a Node or Property: type, mixins, value, and later locking status, versions, etc.

Provide RESTful URLs to access each Node and Property.

Allow Nodes and Properties to be created, updated, deleted, and moved around the tree.

When creating a Node, allow its nodetype to be specified.

Allow mixins to be added to a Node later on.

Handle the JCR Session save/abort concept, where a number of changes to Nodes and Properties are only saved when explicitely actioning a "save" command.

Later, use OSGi-based plugins to edit Property values.

The JCR explorer has to be usable for pure JCR repositories (non-Sling), even though the explorer itself would run under Sling (use cases : display the list of available repositories, add/delete/update a new JCR repo, ...).

Technical Issues

Select a good UI framework : Jquery, YUI or GWT ?

I would vote for Dojo. It has a dojo.data API (similar purpose to JDO/JPA+beansbinding), that can be used to connect to Sling using HTTP, and to the widgets using data binding. Hopefully Sling can also expose a "standard protocol" that can be used with Dojo's JsonRestStore.

Example of a Dojo app, using dojo.data API, backend by a REST store, using SOFEA approach: http://www.persvr.org/explorer.html

~ Hendy Irawan

  • No labels