RichFaces
  1. RichFaces
  2. RF-7571

Client-side library: make code compatible with Portlet environment

    Details

    • Type: Task Task
    • Status: Resolved Resolved (View Workflow)
    • Priority: Major Major
    • Resolution: Rejected
    • Affects Version/s: 4.0.0.ALPHA1
    • Fix Version/s: 4.0.0.CR1
    • Component/s: component, core, portal
    • Security Level: Public (Everyone can see)
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

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

        Issue Links

          Activity

          Hide
          Jay Balunas
          added a comment -

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

          Show
          Jay Balunas
          added a comment - Alex - I need you to at least review this before CR2 is completed.
          Hide
          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
          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
          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
          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
          Alexander Smirnov
          added a comment -

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

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

            People

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

              Dates

              • Created:
                Updated:
                Resolved: