cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "solprovider (JIRA)" <j...@apache.org>
Subject [jira] Closed: (COCOON-2067) CocoonServlet error message names wrong parameter: configurations
Date Mon, 24 Dec 2007 22:27:43 GMT

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

solprovider closed COCOON-2067.
-------------------------------

                     Resolution: Fixed
                  Fix Version/s: 2.1.11-dev (Current SVN)
    Affects version (Component): Parent values: Cocoon Core(10151). 
        Fix version (Component): Parent values: Cocoon Core(10227). 

Added 's'.  
Committed 20071224 revision 606745 for 2.1.11.

> CocoonServlet error message names wrong parameter: configurations
> -----------------------------------------------------------------
>
>                 Key: COCOON-2067
>                 URL: https://issues.apache.org/jira/browse/COCOON-2067
>             Project: Cocoon
>          Issue Type: Bug
>          Components: * Cocoon Core
>    Affects Versions: 2.1.10
>            Reporter: solprovider
>            Priority: Trivial
>             Fix For: 2.1.11-dev (Current SVN)
>
>
> The error message in the last line of the code below misnames the parameter as 'configuration'
instead of 'configurations'.
> The easy fix is to add an 's'.
> A better fix would move the string to a constant for use in all the code below
> [Obviously excerpted code.  Pretend ellipses are after each line.]
> public class CocoonServlet extends HttpServlet { 
>   public void init(ServletConfig conf) throws ServletException {
>       this.appContext.put(Constants.CONTEXT_CONFIG_URL, getConfigFile(conf.getInitParameter("configurations")));
>   }
>     private URL getConfigFile(final String configFileName) throws ServletException {
>             getLogger().warn("Servlet initialization argument 'configurations' not specified,
attempting to use '/WEB-INF/cocoon.xconf'");
>          getLogger().debug("Using configuration file: " + usedFileName);
>          String msg = "Init parameter 'configurations' is invalid : " + usedFileName;
>                String msg = "Init parameter 'configurations' is invalid : " + usedFileName;
>          String msg = "Init parameter 'configuration' doesn't name an existing resource
: " + usedFileName;
>    }
> }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message