You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Craig Doremus (JIRA)" <ji...@apache.org> on 2006/05/05 21:44:28 UTC

[jira] Reopened: (PLUTO-239) Mismatching error message key/translation pair resulting to ambiquous log entry.

     [ http://issues.apache.org/jira/browse/PLUTO-239?page=all ]
     
Craig Doremus reopened PLUTO-239:
---------------------------------


I fixed the causes of the MissingResourceException, not the exception handling mechanism, which will be deferred untill after 1.1-beta1 gets out the door

> Mismatching error message key/translation pair resulting to ambiquous log entry.
> --------------------------------------------------------------------------------
>
>          Key: PLUTO-239
>          URL: http://issues.apache.org/jira/browse/PLUTO-239
>      Project: Pluto
>         Type: Bug

>   Components: portlet container
>     Versions: Current CVS
>     Reporter: Tuomas Kiviaho
>     Priority: Trivial
>      Fix For: 1.1.0-beta1

>
> Apache Tomcat produced a following line when request dispacher couldn't be created. 
> ERROR org.apache.pluto.core.PortletInvoker - Cannot find message associated with key error.portlet.invoker.dispatcher
> The given message key (here "error.portlet.invoker.dispatcher", but there are more in the same file) doesn't have a counterpair in LocalString.properties or at least one of them is misspelled.
> The problem is that the original problem is not what is outputted to the log as a result of...
>   try {
>             str = bundle.getString(key);
>   } catch (MissingResourceException mre) {
>             str = "Cannot find message associated with key '" + key + "'";
>   }
> ...but it is either tranlation with arguments inserted or as a fallback just the key followed by all of the arguments. If translation is missing that should in my opinion be a separate log entry preferrably just as warning.
>  

-- 
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