Trinidad Filter causes portlet to fail with "The expected request type is not
the same as the current request type."
--------------------------------------------------------------------------------------------------------------------
Key: TRINIDAD-1842
URL: https://issues.apache.org/jira/browse/TRINIDAD-1842
Project: MyFaces Trinidad
Issue Type: Bug
Components: Portlet
Affects Versions: 1.2.14-core
Environment: Mac, Tomcat 6.0.20, Myfaces 1.2.8, Pluto 2.0.2, Portlet
Bridge 2.0 alpha 2.
Reporter: Andrew Redman
If the Trinidad filter is registered against the Portlet Servlet for Pluto, the
request type put in the trinidad state duing filter processing is SERVLET. When
the portlet is invoked the request type is compared to that in the state and at
this point it is PORTLET and so fails the test in the GlobalConfiguratorImpl
getExternalContext giving the following error "The expected request type is not
the same as the current request type.". This used to work but I suspect that
the issue is really that there should be a trindad portlet filter which
operates at portlet level and never at servlet level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
