You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Serg Maslyukov (http://webmill.askmore.info) (JIRA)" <de...@myfaces.apache.org> on 2006/04/28 13:09:37 UTC

[jira] Created: (MYFACES-1294) Current logic of register extensionFilter not support portlet environment

Current logic of register extensionFilter not support portlet environment
-------------------------------------------------------------------------

         Key: MYFACES-1294
         URL: http://issues.apache.org/jira/browse/MYFACES-1294
     Project: MyFaces Core
        Type: Bug

  Components: Portlet_Support  
    Versions: 1.1.4-SNAPSHOT    
    Reporter: Serg Maslyukov (http://webmill.askmore.info)
    Priority: Blocker


Current logic of register extensionFilter not support portlet environment

fiter mappings:

<filter-mapping>
    <filter-name>MyFacesExtensionsFilter</filter-name>
    <servlet-name>Faces Servlet</servlet-name>
</filter-mapping>
<filter-mapping>
    <filter-name>MyFacesExtensionsFilter</filter-name>
    <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
</filter-mapping>
<filter-mapping>
    <filter-name>MyFacesExtensionsFilter</filter-name>
    <url-pattern>*.jsf</url-pattern>
</filter-mapping>


not work in portlet environment

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Re: [jira] Commented: (MYFACES-1294) Current logic of register extensionFilter not support portlet environment

Posted by Arash Rajaeeyan <ar...@gmail.com>.
tell me more I willing to do every thing to support portlets!

On 9/12/06, Martin Marinschek (JIRA) <de...@myfaces.apache.org> wrote:
>
>    [
> http://issues.apache.org/jira/browse/MYFACES-1294?page=comments#action_12433996]
>
> Martin Marinschek commented on MYFACES-1294:
> --------------------------------------------
>
> Filter --> PhaseListener and all our Portlet issues are solved. Anyone
> fancy doing this?
>
> regards,
>
> Martin
>
> > Current logic of register extensionFilter not support portlet
> environment
> >
> -------------------------------------------------------------------------
> >
> >                 Key: MYFACES-1294
> >                 URL: http://issues.apache.org/jira/browse/MYFACES-1294
> >             Project: MyFaces Core
> >          Issue Type: Bug
> >          Components: Portlet_Support
> >    Affects Versions: 1.1.4-SNAPSHOT
> >            Reporter: Serg Maslyukov (http://webmill.askmore.info)
> >            Priority: Blocker
> >
> > Current logic of register extensionFilter not support portlet
> environment
> > fiter mappings:
> > <filter-mapping>
> >     <filter-name>MyFacesExtensionsFilter</filter-name>
> >     <servlet-name>Faces Servlet</servlet-name>
> > </filter-mapping>
> > <filter-mapping>
> >     <filter-name>MyFacesExtensionsFilter</filter-name>
> >     <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
> > </filter-mapping>
> > <filter-mapping>
> >     <filter-name>MyFacesExtensionsFilter</filter-name>
> >     <url-pattern>*.jsf</url-pattern>
> > </filter-mapping>
> > not work in portlet environment
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>


-- 
Arash Rajaeeyan

[jira] Commented: (MYFACES-1294) Current logic of register extensionFilter not support portlet environment

Posted by "Andreas Wiesauer (JIRA)" <de...@myfaces.apache.org>.
    [ http://issues.apache.org/jira/browse/MYFACES-1294?page=comments#action_12434180 ] 
            
Andreas Wiesauer commented on MYFACES-1294:
-------------------------------------------

Hello Martin,

could you give any hints (information, links) about the solution you mentioned. I would be very interested in taking a look at it.

Thanks,
Andy

> Current logic of register extensionFilter not support portlet environment
> -------------------------------------------------------------------------
>
>                 Key: MYFACES-1294
>                 URL: http://issues.apache.org/jira/browse/MYFACES-1294
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: Portlet_Support
>    Affects Versions: 1.1.4-SNAPSHOT
>            Reporter: Serg Maslyukov (http://webmill.askmore.info)
>            Priority: Blocker
>
> Current logic of register extensionFilter not support portlet environment
> fiter mappings:
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <servlet-name>Faces Servlet</servlet-name>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>*.jsf</url-pattern>
> </filter-mapping>
> not work in portlet environment

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MYFACES-1294) Current logic of register extensionFilter not support portlet environment

Posted by "Mario Ivankovits (JIRA)" <de...@myfaces.apache.org>.
    [ http://issues.apache.org/jira/browse/MYFACES-1294?page=comments#action_12402405 ] 

Mario Ivankovits commented on MYFACES-1294:
-------------------------------------------

So are you sure the extension filter isnt called?
In the full stack trace, isnt there a hint to the ExtensionsFilter?

Remy told you to correctly delegate to the parent servletRequest:

So in your request wrapper:
    public Object getAttribute( String key ) {
        if (key==null) {
            throw new IllegalArgumentException("Call getAttribute() with
key==null");
        }

        return portletAttributes.get( key );
    }

for any !portletAttributes.containsKey(key) you should delegate to the wrapped instance.
If there is a break between your requestWrapper and the real request this might explain why my check for the DOFILTER_CALLED failes.

> Current logic of register extensionFilter not support portlet environment
> -------------------------------------------------------------------------
>
>          Key: MYFACES-1294
>          URL: http://issues.apache.org/jira/browse/MYFACES-1294
>      Project: MyFaces Core
>         Type: Bug

>   Components: Portlet_Support
>     Versions: 1.1.4-SNAPSHOT
>     Reporter: Serg Maslyukov (http://webmill.askmore.info)
>     Priority: Blocker

>
> Current logic of register extensionFilter not support portlet environment
> fiter mappings:
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <servlet-name>Faces Servlet</servlet-name>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>*.jsf</url-pattern>
> </filter-mapping>
> not work in portlet environment

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (MYFACES-1294) Current logic of register extensionFilter not support portlet environment

Posted by "Serg Maslyukov (http://webmill.askmore.info) (JIRA)" <de...@myfaces.apache.org>.
    [ http://issues.apache.org/jira/browse/MYFACES-1294?page=comments#action_12378657 ] 

Serg Maslyukov (http://webmill.askmore.info) commented on MYFACES-1294:
-----------------------------------------------------------------------

I just tested myfaces-core-1.1.2 with tomahawk-1.1.2 and find what this issue must be addressed to tomahawk, not myfaces-core

tracelog:

java.lang.IllegalStateException: ExtensionsFilter not correctly configured. JSF mapping missing. JSF pages not covered. Please see: http://myfaces.apache.org/tomahawk/extensionsFilter.html
	at org.apache.myfaces.renderkit.html.util.AddResourceFactory.throwExtensionsFilterMissing(AddResourceFactory.java:371)
	at org.apache.myfaces.renderkit.html.util.AddResourceFactory.checkEnvironment(AddResourceFactory.java:333)
	at org.apache.myfaces.renderkit.html.util.AddResourceFactory.getInstance(AddResourceFactory.java:288)
	at org.apache.myfaces.custom.tree2.HtmlTreeRenderer.encodeJavascript(HtmlTreeRenderer.java:608)
	at org.apache.myfaces.custom.tree2.HtmlTreeRenderer.encodeBegin(HtmlTreeRenderer.java:149)
	at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:512)
	at org.apache.myfaces.custom.tree2.UITreeData.encodeBegin(UITreeData.java:243)
	at org.apache.myfaces.shared_impl.renderkit.RendererUtils.renderChild(RendererUtils.java:433)
	at org.apache.myfaces.shared_impl.renderkit.RendererUtils.renderChildren(RendererUtils.java:419)
	at org.apache.myfaces.shared_impl.renderkit.html.HtmlGroupRendererBase.encodeEnd(HtmlGroupRendererBase.java:75)
	at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:536)
	at org.apache.myfaces.shared_impl.renderkit.RendererUtils.renderChild(RendererUtils.java:442)
	at org.apache.myfaces.shared_impl.renderkit.RendererUtils.renderChildren(RendererUtils.java:419)
	at org.apache.myfaces.shared_impl.renderkit.RendererUtils.renderChild(RendererUtils.java:440)
	at org.apache.myfaces.shared_impl.renderkit.html.HtmlGridRendererBase.renderChildren(HtmlGridRendererBase.java:216)
	at org.apache.myfaces.shared_impl.renderkit.html.HtmlGridRendererBase.encodeEnd(HtmlGridRendererBase.java:98)
	at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:536)
	at org.apache.myfaces.shared_impl.renderkit.RendererUtils.renderChild(RendererUtils.java:442)
	at org.apache.myfaces.shared_impl.renderkit.html.HtmlGridRendererBase.renderChildren(HtmlGridRendererBase.java:216)
	at org.apache.myfaces.shared_impl.renderkit.html.HtmlGridRendererBase.encodeEnd(HtmlGridRendererBase.java:98)
	at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:536)
	at javax.faces.webapp.UIComponentTag.encodeEnd(UIComponentTag.java:495)
	at javax.faces.webapp.UIComponentTag.doEndTag(UIComponentTag.java:363)
	at org.apache.myfaces.shared_impl.taglib.UIComponentBodyTagBase.doEndTag(UIComponentBodyTagBase.java:54)
	at org.apache.jsp.riverock.manager.auth.auth_jsp._jspx_meth_h_panelGrid_0(org.apache.jsp.riverock.manager.auth.auth_jsp:340)
	at org.apache.jsp.riverock.manager.auth.auth_jsp._jspx_meth_h_form_0(org.apache.jsp.riverock.manager.auth.auth_jsp:225)
	at org.apache.jsp.riverock.manager.auth.auth_jsp._jspx_meth_f_view_0(org.apache.jsp.riverock.manager.auth.auth_jsp:177)
	at org.apache.jsp.riverock.manager.auth.auth_jsp._jspService(org.apache.jsp.riverock.manager.auth.auth_jsp:103)
	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)


> Current logic of register extensionFilter not support portlet environment
> -------------------------------------------------------------------------
>
>          Key: MYFACES-1294
>          URL: http://issues.apache.org/jira/browse/MYFACES-1294
>      Project: MyFaces Core
>         Type: Bug

>   Components: Portlet_Support
>     Versions: 1.1.4-SNAPSHOT
>     Reporter: Serg Maslyukov (http://webmill.askmore.info)
>     Priority: Blocker

>
> Current logic of register extensionFilter not support portlet environment
> fiter mappings:
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <servlet-name>Faces Servlet</servlet-name>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>*.jsf</url-pattern>
> </filter-mapping>
> not work in portlet environment

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (MYFACES-1294) Current logic of register extensionFilter not support portlet environment

Posted by "Serg Maslyukov (http://webmill.askmore.info) (JIRA)" <de...@myfaces.apache.org>.
    [ http://issues.apache.org/jira/browse/MYFACES-1294?page=comments#action_12402411 ] 

Serg Maslyukov (http://webmill.askmore.info) commented on MYFACES-1294:
-----------------------------------------------------------------------

Mario, look testsuite at http://issues.apache.org/bugzilla/show_bug.cgi?id=39586 

This test suite based on myfaces-example and adapter for run in Pluto. And not included my own code, only MyFaces and Pluto 



> Current logic of register extensionFilter not support portlet environment
> -------------------------------------------------------------------------
>
>          Key: MYFACES-1294
>          URL: http://issues.apache.org/jira/browse/MYFACES-1294
>      Project: MyFaces Core
>         Type: Bug

>   Components: Portlet_Support
>     Versions: 1.1.4-SNAPSHOT
>     Reporter: Serg Maslyukov (http://webmill.askmore.info)
>     Priority: Blocker

>
> Current logic of register extensionFilter not support portlet environment
> fiter mappings:
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <servlet-name>Faces Servlet</servlet-name>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>*.jsf</url-pattern>
> </filter-mapping>
> not work in portlet environment

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (MYFACES-1294) Current logic of register extensionFilter not support portlet environment

Posted by "Serg Maslyukov (http://webmill.askmore.info) (JIRA)" <de...@myfaces.apache.org>.
    [ http://issues.apache.org/jira/browse/MYFACES-1294?page=comments#action_12402397 ] 

Serg Maslyukov (http://webmill.askmore.info) commented on MYFACES-1294:
-----------------------------------------------------------------------

After some investigate, I found what filter not invoked in any case. I think this is bug in tomcat and open issue in tomcat bugzilla:
http://issues.apache.org/bugzilla/show_bug.cgi?id=39546 and
http://issues.apache.org/bugzilla/show_bug.cgi?id=39586

But Remy Maucherat decide, this is not Tomcat issue and close all this bug as invalid.
May be he right and this bug in Pluto container.

In this case, I think, the best way is to discuss with Pluto team and Remy.


> Current logic of register extensionFilter not support portlet environment
> -------------------------------------------------------------------------
>
>          Key: MYFACES-1294
>          URL: http://issues.apache.org/jira/browse/MYFACES-1294
>      Project: MyFaces Core
>         Type: Bug

>   Components: Portlet_Support
>     Versions: 1.1.4-SNAPSHOT
>     Reporter: Serg Maslyukov (http://webmill.askmore.info)
>     Priority: Blocker

>
> Current logic of register extensionFilter not support portlet environment
> fiter mappings:
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <servlet-name>Faces Servlet</servlet-name>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>*.jsf</url-pattern>
> </filter-mapping>
> not work in portlet environment

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (MYFACES-1294) Current logic of register extensionFilter not support portlet environment

Posted by "Mario Ivankovits (JIRA)" <de...@myfaces.apache.org>.
    [ http://issues.apache.org/jira/browse/MYFACES-1294?page=comments#action_12378679 ] 

Mario Ivankovits commented on MYFACES-1294:
-------------------------------------------

This exception happens if the request didnt pass the extensions filter. This isnt checked by parsing the web.xml, but a simple request property will be checked. The extensionsFilter sets this request property.

if (!extctx.getRequestMap().containsKey(ExtensionsFilter.DOFILTER_CALLED))
{
    throwExtensionsFilterMissing("JSF mapping missing. JSF pages not covered.");
}

Any idea why this wont work?
The only case is, that the request is somehow different scoped in an portlet environment.

When you disable the check (configure init-param org.apache.myfaces.CHECK_EXTENSIONS_FILTER to false) will the myfaces portlet work?
E.g. the inputCalendar or tree2 or the dummyForm stuff?

> Current logic of register extensionFilter not support portlet environment
> -------------------------------------------------------------------------
>
>          Key: MYFACES-1294
>          URL: http://issues.apache.org/jira/browse/MYFACES-1294
>      Project: MyFaces Core
>         Type: Bug

>   Components: Portlet_Support
>     Versions: 1.1.4-SNAPSHOT
>     Reporter: Serg Maslyukov (http://webmill.askmore.info)
>     Priority: Blocker

>
> Current logic of register extensionFilter not support portlet environment
> fiter mappings:
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <servlet-name>Faces Servlet</servlet-name>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>*.jsf</url-pattern>
> </filter-mapping>
> not work in portlet environment

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (MYFACES-1294) Current logic of register extensionFilter not support portlet environment

Posted by "Michael Lipp (JIRA)" <de...@myfaces.apache.org>.
    [ http://issues.apache.org/jira/browse/MYFACES-1294?page=comments#action_12434187 ] 
            
Michael Lipp commented on MYFACES-1294:
---------------------------------------

I don't think this can be moved to a PhaseListener. The point simply is that no portlet application has access to the complete HTML produced by the portal; it can only contribute to the HTML of its portlet. Sure, you could demand that Tomahawk users put the extension filter in the web.xml of the *portal*. But first, I think this is not acceptable (you should be able to deploy a portlet into a running portal), second, you'll get classpath problems, and third the approach to post-fix the generated HTML isn't very clever anyway.

Please do have a look at the solution that I have just posted as comment to TOMAHAWK-464. (I thought the ExtensionFilter issue was to be continued as a Tomahawk issue, because the ExtensionFilter is not part of MyFaces Core.)

You'll find in there the required JavaScript sequences to achieve the same results in the generated HTML without filtering it. There is an AddResource implementation that has been tested for portlets and should be easily adaptable for stand-alone application (the "generation" calls of the AddResource API are ExtensionFilter specific, so I had to add some for the portlet environment). Eventually, it should be possible to avoid a configurable AddResource all together, because the default version works in both the servlet and portlet context.

> Current logic of register extensionFilter not support portlet environment
> -------------------------------------------------------------------------
>
>                 Key: MYFACES-1294
>                 URL: http://issues.apache.org/jira/browse/MYFACES-1294
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: Portlet_Support
>    Affects Versions: 1.1.4-SNAPSHOT
>            Reporter: Serg Maslyukov (http://webmill.askmore.info)
>            Priority: Blocker
>
> Current logic of register extensionFilter not support portlet environment
> fiter mappings:
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <servlet-name>Faces Servlet</servlet-name>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>*.jsf</url-pattern>
> </filter-mapping>
> not work in portlet environment

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MYFACES-1294) Current logic of register extensionFilter not support portlet environment

Posted by "Serg Maslyukov (http://webmill.askmore.info) (JIRA)" <de...@myfaces.apache.org>.
    [ http://issues.apache.org/jira/browse/MYFACES-1294?page=comments#action_12414430 ] 

Serg Maslyukov (http://webmill.askmore.info) commented on MYFACES-1294:
-----------------------------------------------------------------------

I added the result of investigating of problem with filter on WebSpherePortal

http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?nav=false&forum=168&thread=119249&cat=9

This looks like no one portlet container invoke filer in RequestDispather

> Current logic of register extensionFilter not support portlet environment
> -------------------------------------------------------------------------
>
>          Key: MYFACES-1294
>          URL: http://issues.apache.org/jira/browse/MYFACES-1294
>      Project: MyFaces Core
>         Type: Bug

>   Components: Portlet_Support
>     Versions: 1.1.4-SNAPSHOT
>     Reporter: Serg Maslyukov (http://webmill.askmore.info)
>     Priority: Blocker

>
> Current logic of register extensionFilter not support portlet environment
> fiter mappings:
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <servlet-name>Faces Servlet</servlet-name>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>*.jsf</url-pattern>
> </filter-mapping>
> not work in portlet environment

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (MYFACES-1294) Current logic of register extensionFilter not support portlet environment

Posted by "Martin Marinschek (JIRA)" <de...@myfaces.apache.org>.
    [ http://issues.apache.org/jira/browse/MYFACES-1294?page=comments#action_12433996 ] 
            
Martin Marinschek commented on MYFACES-1294:
--------------------------------------------

Filter --> PhaseListener and all our Portlet issues are solved. Anyone fancy doing this?

regards,

Martin

> Current logic of register extensionFilter not support portlet environment
> -------------------------------------------------------------------------
>
>                 Key: MYFACES-1294
>                 URL: http://issues.apache.org/jira/browse/MYFACES-1294
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: Portlet_Support
>    Affects Versions: 1.1.4-SNAPSHOT
>            Reporter: Serg Maslyukov (http://webmill.askmore.info)
>            Priority: Blocker
>
> Current logic of register extensionFilter not support portlet environment
> fiter mappings:
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <servlet-name>Faces Servlet</servlet-name>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
> </filter-mapping>
> <filter-mapping>
>     <filter-name>MyFacesExtensionsFilter</filter-name>
>     <url-pattern>*.jsf</url-pattern>
> </filter-mapping>
> not work in portlet environment

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira