[jira] Created: (SLING-766) Initial Content should not be removed on bundle stop
Initial Content should not be removed on bundle stop Key: SLING-766 URL: https://issues.apache.org/jira/browse/SLING-766 Project: Sling Issue Type: Bug Components: JCR Contentloader Affects Versions: JCR Contentloader 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Jackrabbit Server 2.0.4 Currently the initial content is removed on a bundle stop - while this is logically ok (content is installed on bundle start, and content shouldn't be available when bundle is not running anymore), this creates problems when the server is shutdown as the bundle is stopped and therefore removes all content on shutdown. (of course the content is added again on server startup) Therefore it's better to remove the content only when the bundle is uninstalled. As a consequence of not uninstalling the initial content anymore when the bundle is stopped, content update when the bundle is updated must be adapted and take care on properly replacing old content with new content. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-766) Initial Content should not be removed on bundle stop
[ https://issues.apache.org/jira/browse/SLING-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-766: --- Fix Version/s: (was: JCR Jackrabbit Server 2.0.4) JCR Contentloader 2.0.4 > Initial Content should not be removed on bundle stop > > > Key: SLING-766 > URL: https://issues.apache.org/jira/browse/SLING-766 > Project: Sling > Issue Type: Bug > Components: JCR Contentloader >Affects Versions: JCR Contentloader 2.0.2 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: JCR Contentloader 2.0.4 > > > Currently the initial content is removed on a bundle stop - while this is > logically ok (content is installed on bundle start, and content shouldn't be > available when bundle is not running anymore), this creates problems when the > server is shutdown as the bundle is stopped and therefore removes all content > on shutdown. > (of course the content is added again on server startup) > Therefore it's better to remove the content only when the bundle is > uninstalled. As a consequence of not uninstalling the initial content anymore > when the bundle is stopped, content update when the bundle is updated must be > adapted and take care on properly replacing old content with new content. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Data Validation
Hi Darrell, On Tue, Dec 9, 2008 at 6:22 PM, Darrell Pittman <[EMAIL PROTECTED]> wrote: > ...I see what I have to do, thanks. Is there any plan to > incorporate some kind of validation functionality in the future?... I don't think we have a concrete plan to do that, but a validation framework would IMHO be a nice thing to have in Sling. A request filter that validates request parameters, combined with a utility that makes it easy for scripts to use request parameters values and validation errors to fill form fields instead of using the current node's values, is probably all that's needed. I would make the filter generic and use OSGi services and/or server-side scripts to define specific validations. As usual, contributions are welcome - I don't think any of the current committers is working on that at the moment, but if you want to propose a solution we can certainly help with design and review. -Bertrand
[jira] Resolved: (SLING-767) Provide better configurability and integration for WebDAV
[ https://issues.apache.org/jira/browse/SLING-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-767. - Resolution: Fixed Implemented this change in Rev. 725679. Updating Documentation > Provide better configurability and integration for WebDAV > - > > Key: SLING-767 > URL: https://issues.apache.org/jira/browse/SLING-767 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR Webdav 2.0.2 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: JCR Webdav 2.0.4 > > > The current implementation of (simple) WebDAV support only provide little > support for configuration of the inner operations. In addition MIME type > resolution is not integrated with Sling support MIME type resolution. > To fix this, Sling WebDAV should add its own configuration by means of > extending the Jackrabbit ResourceConfig class and overwriting all methods > along these lines: > * MIME Type resolution is delegated to Sling's MIME type resolution by > providing a SlingMimeResolver > * IOManager and PropertyManager are hard coded to use the default > implementations > * Only DirListingExportHandler and DefaultHandler are registered and used > * Configuration through OSGi Configuration Admin is defined. > The following configuration is possible and supported: > - node types defining non-collection resources > - item filter setting by namespace uri and prefix and node type > - node types for collection, non-collection and content nodes > - (as before) Realm String and URL root for the separate WebDAV servlet -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-767) Provide better configurability and integration for WebDAV
Provide better configurability and integration for WebDAV - Key: SLING-767 URL: https://issues.apache.org/jira/browse/SLING-767 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Webdav 2.0.2 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR Webdav 2.0.4 The current implementation of (simple) WebDAV support only provide little support for configuration of the inner operations. In addition MIME type resolution is not integrated with Sling support MIME type resolution. To fix this, Sling WebDAV should add its own configuration by means of extending the Jackrabbit ResourceConfig class and overwriting all methods along these lines: * MIME Type resolution is delegated to Sling's MIME type resolution by providing a SlingMimeResolver * IOManager and PropertyManager are hard coded to use the default implementations * Only DirListingExportHandler and DefaultHandler are registered and used * Configuration through OSGi Configuration Admin is defined. The following configuration is possible and supported: - node types defining non-collection resources - item filter setting by namespace uri and prefix and node type - node types for collection, non-collection and content nodes - (as before) Realm String and URL root for the separate WebDAV servlet -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-767) Provide better configurability and integration for WebDAV
[ https://issues.apache.org/jira/browse/SLING-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-767. --- Updated documentation at [1] (should be online in a few hours) Closing this issue now. [1] http://incubator.apache.org/sling/site/repository-based-development.html#RepositoryBasedDevelopment-WebDAVSupport > Provide better configurability and integration for WebDAV > - > > Key: SLING-767 > URL: https://issues.apache.org/jira/browse/SLING-767 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR Webdav 2.0.2 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: JCR Webdav 2.0.4 > > > The current implementation of (simple) WebDAV support only provide little > support for configuration of the inner operations. In addition MIME type > resolution is not integrated with Sling support MIME type resolution. > To fix this, Sling WebDAV should add its own configuration by means of > extending the Jackrabbit ResourceConfig class and overwriting all methods > along these lines: > * MIME Type resolution is delegated to Sling's MIME type resolution by > providing a SlingMimeResolver > * IOManager and PropertyManager are hard coded to use the default > implementations > * Only DirListingExportHandler and DefaultHandler are registered and used > * Configuration through OSGi Configuration Admin is defined. > The following configuration is possible and supported: > - node types defining non-collection resources > - item filter setting by namespace uri and prefix and node type > - node types for collection, non-collection and content nodes > - (as before) Realm String and URL root for the separate WebDAV servlet -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
user management
Even though user management will not be part of sling it would be good to have a common implementation. So I'm wondering if anyone else is working on something here, and / or if this would fit into a sort of sling-commons project. With user management I'm thinking about; glue between login form page and jcr authenticatio user node type definitions with most common properties for basic users; uid, password, basic group node types basic manager for managing users and groups; add/remove/update, change group membership. -- Torgeir Veimo torg...@pobox.com
