Hi,
On Sat, Dec 12, 2015 at 5:47 PM, Peter Hunsberger
<[email protected]> wrote:
> ...I see. I had assumed a more functional style with the state travelling
> with the return value, that then get's chained to the next call....
I have modified the ResourceBuilder interface to work in this way, so
you can now do
final Resource r = resourceResolver.getResource("/apps");
builderService.forParent(r).resource("1/2);
builderService.forParent(r).resource("3/4");
To create both /apps/1/2 and /apps/3/4.
Basically you need to use either forResolver(ResourceResolver r) or
forParent(Resource r) on the ResourceBuilder service to get a stateful
ResourceBuilder, where you can then chain calls but not call the for*
methods again.
Is that closer to what you expected, or do you have a better idea?
-Bertrand
