You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2010/12/01 18:19:11 UTC

[jira] Resolved: (MYFACES-2983) Consider using myfaces class's classloader when loading resources

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

Leonardo Uribe resolved MYFACES-2983.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.3-SNAPSHOT
         Assignee: Leonardo Uribe

The problem related to the test was committed.

Thanks to David Jencks for provide this patch.

> Consider using myfaces class's classloader when loading resources
> -----------------------------------------------------------------
>
>                 Key: MYFACES-2983
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2983
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 2.0.3-SNAPSHOT
>            Reporter: David Jencks
>            Assignee: Leonardo Uribe
>             Fix For: 2.0.3-SNAPSHOT
>
>         Attachments: MYFACES-2983-2.patch
>
>
> There are a few instances where only the TCCL is considered for loading resources that are actually in a myfaces jar.  This won't work in an isolated classes environment like OSGI.  A simple fix is to try the TCCL and if it doesn't work try the cl that loads myfaces classes.  This solves the problem in geronimo's OSGI environment but I wonder if only the cl for myfaces classes should be considered in many of these cases since it looks like the resource being loaded is often a known file packed in with myfaces that can't be replaced by a user supplied resource.

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