Uploaded image for project: 'RichFaces'
  1. RichFaces
  2. RF-7571

Client-side library: make code compatible with Portlet environment

    Details

    • Similar Issues:
      Show 10 results 

      Description

      use anonimous functions to hide internal code, pass all public methods names with ExternalContext.encodeNamespace().

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            jbalunas Jay Balunas added a comment -

            Alex - I need you to at least review this before CR2 is completed.

            Show
            jbalunas Jay Balunas added a comment - Alex - I need you to at least review this before CR2 is completed.
            Hide
            jbalunas Jay Balunas added a comment - - edited

            Based on discussions with Nick, the required steps for this is too risky and complex for this stage of the release. We will need to review and plan for portlet support in a near term future release.

            Nick:

            What we need to get this working in portlets
            1) use module pattern in JS - already done
            2) overwrite CSS class names - add portlet namespaces to them - affects renderer code & CSS files
            3) overwrite CSS class names in JavaScript - this is I believe the trickiest part

            Either we 1) overwrite or 2) externalize class names into hash passed into module pattern constructor

            These 2) & 3) parts affects almost all components - and I expected this to be covered by unified approach backed by CDK

            Show
            jbalunas Jay Balunas added a comment - - edited Based on discussions with Nick, the required steps for this is too risky and complex for this stage of the release. We will need to review and plan for portlet support in a near term future release. Nick: What we need to get this working in portlets 1) use module pattern in JS - already done 2) overwrite CSS class names - add portlet namespaces to them - affects renderer code & CSS files 3) overwrite CSS class names in JavaScript - this is I believe the trickiest part Either we 1) overwrite or 2) externalize class names into hash passed into module pattern constructor These 2) & 3) parts affects almost all components - and I expected this to be covered by unified approach backed by CDK
            Hide
            jbalunas Jay Balunas added a comment -

            Alex - please update this jira with the latest information from your investigation, and resolve when you feel compatibility is good enough for 4.0

            Show
            jbalunas Jay Balunas added a comment - Alex - please update this jira with the latest information from your investigation, and resolve when you feel compatibility is good enough for 4.0
            Hide
            alexsmirnov Alexander Smirnov added a comment -

            That really has to be part of JSF 2.x related bridge spec.

            Show
            alexsmirnov Alexander Smirnov added a comment - That really has to be part of JSF 2.x related bridge spec.

              People

              • Assignee:
                alexsmirnov Alexander Smirnov
                Reporter:
                abelevich Anton Belevich
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development