[jira] Created: (SLING-730) Getter for JcrResourceResolverFactoryImpl.rootProviderEntry

Getter for JcrResourceResolverFactoryImpl.rootProviderEntry --- Key: SLING-730 URL: https://issues.apache.org/jira/browse/SLING-730 Project: Sling Issue Type: Improvement

[jira] Updated: (SLING-730) Getter for JcrResourceResolverFactoryImpl.rootProviderEntry

[ https://issues.apache.org/jira/browse/SLING-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vidar S. Ramdal updated SLING-730: -- Attachment: JcrResourceResolverFactoryImpl.diff Patch for JcrResourceResolverFactoryImpl

Re: JcrResourceResolverFactoryImpl#getRootProviderEntry()

Vidar Ramdal schrieb: [...] So: Can I introduce a protected getRootProviderEntry() in JcrResourceResolverFactoryImpl, please? [...] If you're OK with it, I'll create a JIRA task and a patch. On Thu, Nov 13, 2008 at 4:27 PM, Felix Meschberger [EMAIL PROTECTED] wrote: Would be great. Thanks.

[jira] Created: (SLING-731) Active bundles queue must be reprocessed if bundle.start() fails

Active bundles queue must be reprocessed if bundle.start() fails Key: SLING-731 URL: https://issues.apache.org/jira/browse/SLING-731 Project: Sling Issue Type: Bug

[jira] Commented: (SLING-731) Active bundles queue must be reprocessed if bundle.start() fails

[ https://issues.apache.org/jira/browse/SLING-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12647342#action_12647342 ] Bertrand Delacretaz commented on SLING-731: --- Fixed in revision 713758, and the

A bug in parameter encoding

Hi guys, I think there is a bug in sling's parameter encoding handling. It even fails at simple sample. Like this: form action=/contents/hello method=post input name=test value=测试/ input type=hidden name=_charset_ value=utf-8 / /form The cause of this problem is simple. When

Re: Replacing JcrResourceResolverFactory by a Sling ResourceResolverFactory

Hi, Carsten Ziegeler schrieb: I like the proposal :) Thanks ;-) I've a few comments. I think we don't need constants for workspace or session for the login stuff. At least the workspace should/could be a configuration of the jcr resource resolver factory. One the one hand, this is true,

Re: Replacing JcrResourceResolverFactory by a Sling ResourceResolverFactory

Hi Juanjo, Juanjo Vázquez schrieb: The proposal also allows for much more flexibility in building the Resource tree made of ResourceProviders where each ResourceProvider itself may actually be provided by a ResourceProviderFactory. Felix, this implementation would allow to have an only

Re: Replacing JcrResourceResolverFactory by a Sling ResourceResolverFactory

Hi David, David Nuescheler schrieb: what i would strongly caution though is fostering the divergence between the resource tree and the node tree. since there are good tools to browse, search and manage the node tree this is really one of the main advantages that sling brings to the table