[
https://jira.jboss.org/jira/browse/RF-7189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Balunas updated RF-7189:
----------------------------
Fix Version/s: Future
> PortletResponse.encodeURL not being called causes WSRP not to work
> ------------------------------------------------------------------
>
> Key: RF-7189
> URL: https://jira.jboss.org/jira/browse/RF-7189
> Project: RichFaces
> Issue Type: Bug
> Components: portal
> Affects Versions: 3.3.1
> Environment: WebSphere Application Server 7 w/WSRP provider
> installed, WebSphere Portal Server 6.1
> Reporter: David Holscher
> Assignee: Alexander Smirnov
> Fix For: Future
>
>
> A portlet that does work using the portlet provider in WebSphere Application
> Server 7 does not work when the same portlet is published to WebSphere Portal
> Server 6.1 using WSRP (portlet is installed in Application Server and
> provided to Portal Server through WSRP).
> There doesn't appear to be a problem with WebSphere itself, the problem
> appears to be with URLs for scripts that are served up. The call to
> PortletResponse.encodeURL is supposed to correct these URLs but it only gets
> called for some resources. There appears to be weird behaviour in the
> ResourceBuilderImpl class that checks if a resource is global before calling
> encodeResourceURL on the ExternalContext (which in turn calls
> PortletResponse.encodeURL in a portal environment). This selective use of
> encodeResourceURL seems to go against the use documented in the
> specification.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
