Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <3692810.1156973843247.JavaMail.jira@brutus>
Date: Wed, 30 Aug 2006 14:37:23 -0700 (PDT)
From: "Lars Trieloff (JIRA)" <jira@apache.org>
To: dev@cocoon.apache.org
Subject: [jira] Updated: (COCOON-1905) [PATCH] Support non-file resources
 for jaas.config in JCR block
In-Reply-To: <30479486.1156973602351.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/COCOON-1905?page=all ]

Lars Trieloff updated COCOON-1905:
----------------------------------

    Attachment: cocoon-jcr-jaas-uri-source.patch

This patch allows the JAAS configuration to be stored in non physical files, e.g. in context resources, which is often the case with blocks under development that are deployed using the mvn cocoon:deploy goal.

The patch adds a special case for those non-physical files: A temporary file is created, the contents of the specified resource are copied into the temporary file and this temporary file is used for configuring JAAS.

This is very convenient behaviour in development environments because the block can be used out-of-the-box, but does not affect the security properties of a production system because in this case the location of the jaas.config file will be specified using Java system properties.

> [PATCH] Support non-file resources for jaas.config in JCR block
> ---------------------------------------------------------------
>
>                 Key: COCOON-1905
>                 URL: http://issues.apache.org/jira/browse/COCOON-1905
>             Project: Cocoon
>          Issue Type: Improvement
>          Components: Blocks: (Undefined)
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Lars Trieloff
>            Priority: Minor
>         Attachments: cocoon-jcr-jaas-uri-source.patch
>
>
> The current implementation of the JCR-block requires the user to define a physical file as source for the jaas.config. While is behaviour matches the requirements of the Java JAAS implementation it is inconvenient for development and prevents the creation of a generic out-of-the-box cocoon-JCR-example.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira