[jira] Closed: (SLING-612) When several jobs of the same time are run in parallel, these are tried without a wait time in a cycle

[ https://issues.apache.org/jira/browse/SLING-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-612. -- Resolution: Fixed When several jobs of the same time are run in parallel, these are tried

[jira] Updated: (SLING-606) Event to cancel a job

[ https://issues.apache.org/jira/browse/SLING-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-606: --- Fix Version/s: Extensions Event 2.0.4 Event to cancel a job -

[jira] Reopened: (SLING-571) JspServletWrapper swallows jsp exceptions if root cause is null

[ https://issues.apache.org/jira/browse/SLING-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reopened SLING-571: Reopen this bug so we don't forget it JspServletWrapper swallows jsp exceptions if root

[jira] Created: (SLING-616) Provide better filter options to search for job

Provide better filter options to search for job --- Key: SLING-616 URL: https://issues.apache.org/jira/browse/SLING-616 Project: Sling Issue Type: New Feature Components: Event

Script resolution based on node types in /libs/*/my/type instead of just /libs/my/type?

Hi all, if you use both the standard servlet/script resolution using an explicit resource type (eg. myapp/foobar) and sometimes (for convenience) via the node type (eg. my:type) you get mixed locations for both scripts: /libs/myapp/foobar /libs/my/type Often you'd like to put them together,

Re: Script resolution based on node types in /libs/*/my/type instead of just /libs/my/type?

Hi, Alexander Klimetschek schrieb: Hi all, if you use both the standard servlet/script resolution using an explicit resource type (eg. myapp/foobar) and sometimes (for convenience) via the node type (eg. my:type) you get mixed locations for both scripts: /libs/myapp/foobar /libs/my/type

Re: Script resolution based on node types in /libs/*/my/type instead of just /libs/my/type?

On Fri, Aug 15, 2008 at 3:54 PM, Felix Meschberger [EMAIL PROTECTED] wrote: Just a quick question: Why don't you set your resource type to be my/foobar or even my:foobar ? So you are at /libs/my/foobar /libs/my/type Because the namespace prefix my is a very generic one (it is cq ;-)),

Re: Script resolution based on node types in /libs/*/my/type instead of just /libs/my/type?

On 8/15/08, Alexander Klimetschek [EMAIL PROTECTED] wrote: Hi all, if you use both the standard servlet/script resolution using an explicit resource type (eg. myapp/foobar) and sometimes (for convenience) via the node type (eg. my:type) you get mixed locations for both scripts:

ClassCircularityError when using LdapLoginModule (updated)

Apologies if this is a repeat, my first post didn't seem to make it: I disabled the SimpleLoginModule in repository.xml and configured a login.conf file with the com.sun.security.auth.module. LdapLoginModule (from JDK 6). After creating LDAP users for the admin anonymous identities, Sling

ClassCircularityError when using LdapLoginModule

I disabled the SimpleLoginModule in repository.xml and configured a login.conf file with the com.sun.security.auth.module.LdapLoginModule (from JDK 6). After creating LDAP users for the admin anonymous identities, Sling starts up fine. However, when requesting a node with a JSP rendering