David,
So this change breaks the JSF demo or is the demo already boken? What kind
of problem are you seeing? Is there an exception that you can share with
me?
What abou the calendar portlet that you had set up twice on the same page?
Can you try that with this patch and see if it causes any problems.
Again we don't use the MyFaces JSF implementation so our environment is
quite different than yours. I am willing to work with you to come up with a
solution to this problem.
- Matt
On 5/17/07, David Sean Taylor (JIRA) <[email protected]> wrote:
[
https://issues.apache.org/jira/browse/PB-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496725]
David Sean Taylor commented on PB-62:
-------------------------------------
im applying this patch, although Im still seeing broken behavior in the
JSF Demo portlet that comes with Bridges (jsf-demo)
leaving this issue open until i can get the jsf-demo and jetspeed-profiler
ui working again
> PortletViewHandler should create a PortletUIViewRoot
> ----------------------------------------------------
>
> Key: PB-62
> URL: https://issues.apache.org/jira/browse/PB-62
> Project: Portals Bridges
> Issue Type: Bug
> Components: jsf
> Environment: Sun JSF Reference Implementation version 1.2 (
jsf-impl.jar)
> Websphere portlet container version 6.1.0
> Apache MyFaces JSF portal bridge version 1.0.1 (
portals-bridges-jsf-1.0.jar)
> Reporter: Matthew Bruzek
> Assigned To: David Sean Taylor
> Fix For: 1.0.1
>
> Attachments: PortletViewHandlerImpl.java,
PortletViewHandlerImpl.java, PortletViewHandlerImpl.java
>
>
> I found a bug in the PortletViewHandlerImpl.createView() and
restoreView() methods. The createView() method creates a
UIViewRoot. UIViewRoot is not a NamingContainer and does not make unique
client ids for the portal environment.
> The PortletViewHandlerImpl is ONLY used in the portal environment and
should create PortletUIViewRoot objects instead of a UIViewRoot objects.
> The Portals Bridges bug PB-35 (
http://issues.apache.org/jira/browse/PB-35 ) addressed a namespacing
problem with the jsf portals bridge. Multiple classes were changed to
create a PortletUIViewRoot to fix the namespacing problem. The
PortletViewHandlerImpl class must have been missed when converting the
bridge to use PortletUIViewRoot.
> I have included a code example on how to fix this problem. Please see
the latest attached file.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
