[jira] Commented: (MYFACES-1870) Portlet support broken

["Scott O'Bryan (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/MYFACES-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592057#action_12592057 ] 

Scott O'Bryan commented on MYFACES-1870:
----------------------------------------

Does this only happen in the 1.2 environments?  If so, the 1.2 bridge is in the process of being deprecated and replaces by the portlet-bridge project which is going to be the R.I. for JSR-301.  

In pre-301 faces, these methods MUST return null.  I *think*, although I'll have to check, that in 301 implementations this is provided.  If we need support for the Pre-301 bridge in the core 1.2 branch, we need to check for nulls returned by these methods throughout.


> Portlet support broken
> ----------------------
>
>                 Key: MYFACES-1870
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1870
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: Portlet_Support
>    Affects Versions:  1.2.0, 1.2.2
>         Environment: IBM JDK 1.5, IBM WebSphere 6.1
>            Reporter: Mathias Werlitz
>
> Implementation of DefaultViewHandlerSupport only works in Servlet environment.
> In getFacesServletMapping() the calls to externalContext.getRequestServletPath() and externalContext.getRequestPathInfo() will both return NULL in a portlet environment and thus resulting in a NPE calculateFacesServletMapping().

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