[
https://issues.apache.org/jira/browse/TOMAHAWK-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601207#action_12601207
]
Christian Koelle commented on TOMAHAWK-1263:
--------------------------------------------
Setting the property com.ibm.ws.webcontainer.invokefilterscompatibility=true
fixed this issue.
[On the German WAS version it can be set here: Anwendungsserver >
<servername>Webcontainer > Benutzerdefinierte Merkmale]
Please note, that I never got a FileNotFound-Exception on the console and I
thought this is a outdated issue.
Nevertheless this has caused a lot of pain. I will submit this to IBM. I will
add this information to the Myfaces Wiki.
Regards, thanks for your quick response.
> ExtensionFilter does not work with Websphere 6.1.0.15
> -----------------------------------------------------
>
> Key: TOMAHAWK-1263
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1263
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Affects Versions: 1.1.6
> Environment: Windows XP SP2
> Rapid Application Developer 7.0.0.6
> Websphere 6.1.0.15 (The updated )
> Websphere-Build-Nummer: cf150808.12
> Websphere Build-Datum: 2/28/08
> Reporter: Christian Koelle
> Assignee: Hazem Saleh
>
> The extension filter does not work in myfaces-tomahawk applications running
> in IBM Websphere Application Server (WAS) 6.1.0.15, which comes along with
> the IBM Rapid-Application-Defeveloper (RAD) 7.0.0.6. The same problem occured
> int WAS 6.1.0.2 which initially comes along with RAD 7.0. WAS 6.1.0.15 is the
> most up-to-date version of WAS for RAD.
> The behaviour can be reproduced with the myfaces demo application. It has to
> be amended, according to the deployment procedures for WAS 6.1 decribed in
> the Myfaces-Wiki [1], i. e.
> - download the Myfaces-examples and take the myfaces-example-simple.war
> application
> - extract the contents
> - remove the commons-logging.XXX.jar from the WEB-INF/lib directory (see [1])
> - repack the application with a zip-programm
> - deploy the application
> - alter the module classloader policy to load classes using the application
> class loader first.
> - go to the starting page
> - Click on TabbedPane > The styles cannot be resolved, contrary to Tomcat
> 5.5.20 and Jetty.
> - Click on JSCookMenu > You will not see a menu at all, as the resources
> cannot be resolved, contrary to Tomcat 5.5.20 and Jetty.
> If this is a Websphere-Bug, please close this bug and assist me in providing
> information für the IBM bug report.
> 'Thanks in advance.
> Regards
> Christian Kölle
> [1] http://wiki.apache.org/myfaces/Websphere_Installation
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
