myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stan Silvert (JIRA)" <myfaces-...@incubator.apache.org>
Subject [jira] Resolved: (MYFACES-226) LoadBundle doesn't specify class loader
Date Thu, 05 May 2005 21:05:05 GMT
     [ http://issues.apache.org/jira/browse/MYFACES-226?page=all ]
     
Stan Silvert resolved MYFACES-226:
----------------------------------

    Resolution: Fixed

> LoadBundle doesn't specify class loader
> ---------------------------------------
>
>          Key: MYFACES-226
>          URL: http://issues.apache.org/jira/browse/MYFACES-226
>      Project: MyFaces
>         Type: Bug
>     Versions: 1.0.9 beta
>     Reporter: Stan Silvert
>     Assignee: Stan Silvert
>     Priority: Critical
>      Fix For: Nightly Build

>
> LoadBundleTag calls ResourceBundle.getBundle(basename, locale) without reference to the
classloader.
> If the JSF tags are loaded as part of a container level tag library then you will get
an error such as:
> 18:03:19,591 WARN  [VariableResolverImpl] Variable 'bundle' could not be resolved.
> Container level tag liberaries are mentioned in the JSP 2.0 spec section 7.3.5.
> To fix this, the context class loader should be passed to the getBundle() method:
> ResourceBundle.getBundle(basename, locale, Thread.currentThread().getContextClassLoader());

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


Mime
View raw message