Uploaded image for project: 'MyFaces Portlet Bridge'
  1. MyFaces Portlet Bridge
  2. PORTLETBRIDGE-55

PortletNamingContainer broken

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.0.0-alpha, 1.0.0-alpha-2, 1.0.0-alpha-3, 1.0.0-beta, 2.0.0-alpha
    • 1.0.0-beta, 2.0.0-alpha
    • Impl
    • None

    Description

      I while back we decided that we would no longer identify that a UIViewRoot was a PortletNamingContainer by whether it implemented an interface or not – rather we switched to using an annotation. When we did this (removed the interface I inadvertently removed the entity that indicated it implemented NamingContainer. I.e. the API provided class didn't "implement NamingContainer". Hence Faces never saw this UIViewRoot as a namingContianer and hence component ids weren't being qualified by the portlet namespace.

      Attachments

        Activity

          People

            mike_freedman Michael Freedman
            mike_freedman Michael Freedman
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: