You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Michal Durdina (JIRA)" <de...@myfaces.apache.org> on 2007/06/21 15:27:47 UTC

[jira] Updated: (MYFACES-1668) Fix for Websphere 5.1

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

Michal Durdina updated MYFACES-1668:
------------------------------------

    Status: Patch Available  (was: Open)

> Fix for Websphere 5.1
> ---------------------
>
>                 Key: MYFACES-1668
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1668
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 1.1.5
>         Environment: Tested with IBM WebSphere Application Server 5.1.1.14 running on IBM JDK 1.4.2 (enclose in WAS) on Windows XP
>            Reporter: Michal Durdina
>            Priority: Minor
>
> Fix for Websphere 5.1. since WAS uses protocol wsjar: for accessing jar content instead of regular protocol jar: 
> This affects FacesConfigurator which does not correctly detect jars on classpath. FacesConfigurator indirectly uses Enumeration resources = ClassLoader.getResources(resource); to detect libraries on classpath and check if they start with prefix jar: what is obviously not true for IBM Websphere :(
> ie. WAS returns wsjar:file:mypath/myjar.jar!xyz where Tomcat returns jar:file:mypath/myjar.jar!xyz
> Patch is provided.

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