[jira] Commented: (SLING-1737) Add state management for resources
[ https://issues.apache.org/jira/browse/SLING-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12908437#action_12908437 ] Carsten Ziegeler commented on SLING-1737: - Updated the configuration state handling and bundle state handling in revisoin 996285 Add state management for resources -- Key: SLING-1737 URL: https://issues.apache.org/jira/browse/SLING-1737 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: OSGi Installer 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: OSGi Installer 3.0.0 Currently there is no state management, so it is hard to tell if a resource has been installed, should be installed, uninstalled etc. In some situations this leads to endless loops where something is tried over and over again - although nothing needs to be done anymore or can't be done. If we add proper state management to the resources, the installer knows what needs to be done and can act accordingly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1737) Add state management for resources
[ https://issues.apache.org/jira/browse/SLING-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12908471#action_12908471 ] Carsten Ziegeler commented on SLING-1737: - Started further refactoring of internal data objects in revision 996317 The EntityResourceList object will get whole state logic for a single entity, this keeps state handling in a single central place (WIP) Add state management for resources -- Key: SLING-1737 URL: https://issues.apache.org/jira/browse/SLING-1737 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: OSGi Installer 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: OSGi Installer 3.0.0 Currently there is no state management, so it is hard to tell if a resource has been installed, should be installed, uninstalled etc. In some situations this leads to endless loops where something is tried over and over again - although nothing needs to be done anymore or can't be done. If we add proper state management to the resources, the installer knows what needs to be done and can act accordingly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Authentication/Authorization and jackrabbit.usermanager functionality
On 12 Sep 2010, at 00:25, Felix Meschberger wrote: There is one situation where an admin session is always retrieved: The CreeateUser servlet. This is probably a bug and should only use an admin session for self-registration. +1, I think we have modified out CreateUser servlet to do this, and added a hook to allow control over self registration, we use that hook to look for things like reCaptcha tokens. Is that something that should be in Sling ? Ian
[jira] Updated: (SLING-1740) Sling Explorer - Displaying/showing server side errors
[ https://issues.apache.org/jira/browse/SLING-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss updated SLING-1740: Attachment: sling-1740-2.patch patch which provides the described functionality (merged with Justin's path commit) Sling Explorer - Displaying/showing server side errors -- Key: SLING-1740 URL: https://issues.apache.org/jira/browse/SLING-1740 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Clemens Wyss Assignee: Mike Müller Priority: Minor Attachments: sling-1740-2.patch Almost all operation of Sling Explorer are performed through Ajax. So far any error that occurred was ignored. This patch makes 'em visible through displaying errors in a modal pop-up-dialog. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
