Return-Path: X-Original-To: apmail-shiro-dev-archive@www.apache.org Delivered-To: apmail-shiro-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ABA6264EC for ; Sat, 2 Jul 2011 23:46:46 +0000 (UTC) Received: (qmail 68519 invoked by uid 500); 2 Jul 2011 23:46:46 -0000 Delivered-To: apmail-shiro-dev-archive@shiro.apache.org Received: (qmail 68432 invoked by uid 500); 2 Jul 2011 23:46:45 -0000 Mailing-List: contact dev-help@shiro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@shiro.apache.org Delivered-To: mailing list dev@shiro.apache.org Received: (qmail 68421 invoked by uid 99); 2 Jul 2011 23:46:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Jul 2011 23:46:45 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Jul 2011 23:46:43 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id D3B0D4427F2 for ; Sat, 2 Jul 2011 23:46:21 +0000 (UTC) Date: Sat, 2 Jul 2011 23:46:21 +0000 (UTC) From: "Les Hazlewood (JIRA)" To: dev@shiro.apache.org Message-ID: <433058659.406.1309650381863.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Created] (SHIRO-310) Improve Quartz Session Validation Scheduler support MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Improve Quartz Session Validation Scheduler support --------------------------------------------------- Key: SHIRO-310 URL: https://issues.apache.org/jira/browse/SHIRO-310 Project: Shiro Issue Type: Improvement Affects Versions: 1.1.0, 1.0.0, 1.2.0 Reporter: Les Hazlewood The current QuartzSessionValidationScheduler doesn't provide any benefit beyond what is already provided by the ExecutorServiceSessionValidationScheduler. It should be easier to configure the Quartz-based SessionValidationScheduler to allow custom Jobs and time scheduling to control exactly when jobs may execute rather than at only a periodic interval (which the ExecutorService-based implementation already does). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira