GitHub user agrajm opened a pull request:

    https://github.com/apache/sling/pull/92

    SLING-4753 - Commit the Resource Resolver before passing it to 
TenantCustomizers for setting up their own customizations

    Persisting the Tenant Resource by calling commit before setting up the 
Tenant Customizers and passing the resolver to them, which potentially have the 
ability to undo all the un-committed changes on the Resolver ( including the 
Tenant Resource itself ) leading to all kind of weird errors like 
InvalidItemStateException , StaleItemStateException etc.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/agrajm/sling trunk

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/sling/pull/92.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #92
    
----
commit 2979825d40644e0c51c0e10c47b3139d181a7c19
Author: Agraj Mangal <[email protected]>
Date:   2015-05-27T07:42:04Z

    SLING-4753 - Commit the Resource Resolver before passing it to Tenant 
Customizers for setting up their own customizations

commit 375f29b74a3ca5b3ba718a9899b902863660cc7a
Author: Agraj Mangal <[email protected]>
Date:   2015-05-27T07:53:23Z

    Revert "SLING-4753 - Commit the Resource Resolver before passing it to 
Tenant Customizers for setting up their own customizations"
    
    This reverts commit 2979825d40644e0c51c0e10c47b3139d181a7c19.

commit fe537e9fed86fb022110f72982938ce8f7c7de75
Author: Agraj Mangal <[email protected]>
Date:   2015-05-27T07:54:23Z

    SLING-4753 - Commit the Resource Resolver before passing it to Tenant 
Customizers for setting up their own customizations

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to