[
https://issues.apache.org/jira/browse/TRINIDAD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610902#action_12610902
]
Michael Oswald commented on TRINIDAD-119:
-----------------------------------------
So I was using the following when developing the workaround filter:
- shale-tiger-1.0.4
- jsf-facelets-1.1.11
- myfaces-api-1.2.2
- myfaces-impl-1.2.2
- trinidad-api-1.2.7
- trinidad-impl-1.2.7
- tomcat-6.0.14
- java-1.6.0_01-b06
I also tried with jsf-api-1.2_02 and jsf-impl-1.2-b19 from sun and the problem
did not exist!
So we are working whith *.xhtml extensions, and so the faces servlet was mapped
to *.xhtml and my MyFacesBugFixFilter was attached with an url-pattern /*. If
you are working with other file extensions, you must change it in my
MyFacesBugFixFilter (it is hardcoded to *.xhtml).
> InputDate popup crashes when using extension mapping
> ----------------------------------------------------
>
> Key: TRINIDAD-119
> URL: https://issues.apache.org/jira/browse/TRINIDAD-119
> Project: MyFaces Trinidad
> Issue Type: Bug
> Affects Versions: 1.2.1-core
> Environment: Apache Tomcat 6.0.13, JDK 1.6.02, Facelets 1.1.11,
> Trinidad 1.2.1, MyFaces 1.2.0, Ajax4jsf 1.0.6
> Reporter: Jan-Kees van Andel
> Attachments: MyFacesBugFixFilter.java
>
>
> If I use extension mapping (*.faces), my inputDate component crashes with a
> 404 when I click on the button.
> The message is:
> "The requested resource (/mblf/__ADFv__) is not available."
> When using prefix mapping (/faces/), everything works fine. The URL it
> references is:
> http://localhost:8080/mblf/faces/__ADFv__?_t=fred&_red=cd&value=1185058800000&loc=en
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
