Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Tue, 4 Sep 2012 20:56:08 +1100 (NCT)
From: "Juan Manuel CABRERA (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <7625515.32082.1346752568265.JavaMail.jiratomcat@arcas>
In-Reply-To: <453133890.828.1346053208773.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (FEDIZ-25) Look for fediz_config.xml in catalina
 base too
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/FEDIZ-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juan Manuel CABRERA updated FEDIZ-25:
-------------------------------------

    Attachment: FederationAuthenticator.java.patch

Hi Glen,
I don't have any definitive opinion about this neither. The enclosed patch searches CATALINA_BASE only, this seems to be the "clean" stand after having read the documentation you pointed me to (thanks for taking time to do so by the way) and corrects 1.
This ends up being a lame patch, but hey! I don't care, this is my first one :)
Regards,
                
> Look for fediz_config.xml in catalina base too
> ----------------------------------------------
>
>                 Key: FEDIZ-25
>                 URL: https://issues.apache.org/jira/browse/FEDIZ-25
>             Project: CXF-Fediz
>          Issue Type: Improvement
>          Components: Plugin
>    Affects Versions: 1.0.0, 1.0.1
>            Reporter: Juan Manuel CABRERA
>            Priority: Trivial
>         Attachments: FederationAuthenticator.java.patch, FederationAuthenticator.java.patch
>
>
> The FederationAuthenticator valve looks for the Fediz configuration file in the catalina_home only, it should be fetched in the catalina_base too to address the cases where both variables are different (which is the case with WTP by default for instance, or in many production deployment)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira