Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.0
    • Fix Version/s: None
    • Component/s: Facelets/VDL
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      700
    • Status Whiteboard:
      Hide

      size_medium importance_large

      Show
      size_medium importance_large

      Description

      If the page author does not specify <h:head> or <h:body> in the template, then
      the VDL implementation should implicitly create the corresponding components and
      place them into the tree where the <head> and <body> tags are found,
      respectively. This allows the resource relocation feature (and other related
      features) to be used without burdening the page author with remembering to add
      <h:head> and <h:body>.

      To have <head> and <body> be translated to <h:head> and <h:body> you just have
      to provide a Facelets TagDecorator (about 15-25 loc) that will replace these two
      tags at template compilation time, so the performance hit should be minimal.

      The question remains, should that TagDecorator be part of an implementation (or
      in case it is part of an implementation, should it be part of the compiler, as
      then there is no need to have it in a Decorator).

        Activity

        Hide
        mojavelinux added a comment -

        Set milestone to 2.1

        Show
        mojavelinux added a comment - Set milestone to 2.1
        Hide
        mojavelinux added a comment -

        Please note that these components should only be created if <body> and <head>
        are found. Obviously, these components may not (should not?) be needed inside of
        a portlet.

        Show
        mojavelinux added a comment - Please note that these components should only be created if <body> and <head> are found. Obviously, these components may not (should not?) be needed inside of a portlet.
        Hide
        Ed Burns added a comment -
            • Issue 702 has been marked as a duplicate of this issue. ***
        Show
        Ed Burns added a comment - Issue 702 has been marked as a duplicate of this issue. ***
        Hide
        Ed Burns added a comment -

        edburns

        Show
        Ed Burns added a comment - edburns
        Hide
        Ed Burns added a comment -

        triage

        Show
        Ed Burns added a comment - triage
        Hide
        Ed Burns added a comment -

        GlassFish 3.1 M6 at the latest.

        Show
        Ed Burns added a comment - GlassFish 3.1 M6 at the latest.
        Hide
        Ed Burns added a comment -

        Move these to 2.2

        Show
        Ed Burns added a comment - Move these to 2.2
        Hide
        Ed Burns added a comment -

        Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.

        Show
        Ed Burns added a comment - Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.

          People

          • Assignee:
            Unassigned
            Reporter:
            mojavelinux
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: