[SLING-5356] New ResourceBuilder module - fluent API to create content structures

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: Resource Builder 1.0.0
• Component/s: Extensions
• Assignee: Bertrand Delacretaz
• Reporter: Bertrand Delacretaz
• Created: 07/Dec/15 13:45
• Updated: 14/Sep/16 21:21
• Resolved: 07/Sep/16 08:08

Description

As discussed recently on our dev list the ContentBuilder currently provided by the Sling Mocks library [1] can be very useful in testing. (edit: while implementing I have diverged from that idea and created a new, more powerful ResourceBuilder API, for now that ContentBuilder stays unchanged).

In order to make it usable for both client-side and server-side testing (as well as in server-side code) I'm planning to

• Extract it into its own module
• Define an API that allows for creating nodes and properties, importing JSON and other files via the Sling ContentLoader and providing a simple a way to cleanup the test content
• Implement (first) a server-side version of that API
• Implement (as a second priority) a client-side version that can be used in test run via HTTP

This shouldn't affect the existing Sling Mocks library users, except maybe forcing them to rebuild their tests to use the new API.

[1] https://sling.apache.org/documentation/development/sling-mock.html#building-content

Issue Links

• is related to: SLING-6040 Add ResourceBuilder Support to sling-mock
• is related to: SLING-5330 add a method to include sling initial content rule in the generated manifest
• is related to: SLING-6035 ResourceBuilder: Support absolute paths
• is related to: SLING-6036 ResourceBuilder: Reusing ResourceBuilder instances
• is related to: SLING-6039 ResourceBuilder: Split up ResourceBuilder and ResourceBuilderFactory