Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0
    • Fix Version/s: 2.1
    • Component/s: OTHER
    • Labels:
      None
    • Environment:

      Operating System: ALL
      Platform: ALL

    • Issuezilla Id:
      79

      Description

      The taglib directive has a tagdir attribute that is used to describe a directory
      for the location of .tag files.

      This seems a clean way to refer to a collection of actions without creating a
      URI just to refer to them. The situation is quite messier for normal custom
      actions, where we overload the semantics of the uri attribute.

      Note that this overload is also breaking transparency: it is quite visible
      whether the custom actions are implemented via a .tag file or via a custom
      action. It is arguable whether that is good or not.

        Activity

        Hide
        Ed Burns added a comment -

        >>>>> On Fri, 17 Dec 2004 10:30:03 -0800, Hans Bergsten
        <hans@GEFIONSOFTWARE.COM> said:

        HB> Just one comment:
        >> I agree. In particular, I think that if there is something to
        >> be gained by having an application level setting for content type
        >> (and I think there is), that the only appropriate place for
        >> that switch is in the JSP layer itself. Frankly, it'd be great
        >> if the JSP spec had a way to say "Look, every last page is going
        >> to be application/xml+html in UTF-8, unless I say otherwise, OK?"
        >> But it makes less sense for JSF to define this sort of thing on behalf
        >> of the JSP layer.

        HB> There is such a switch in JSP 2.0: you can use the <jsp-config>
        HB> element in web.xml to include a file that contains a page
        HB> directive with a contentType attribute in all or some pages.

        Show
        Ed Burns added a comment - >>>>> On Fri, 17 Dec 2004 10:30:03 -0800, Hans Bergsten <hans@GEFIONSOFTWARE.COM> said: HB> Just one comment: >> I agree. In particular, I think that if there is something to >> be gained by having an application level setting for content type >> (and I think there is), that the only appropriate place for >> that switch is in the JSP layer itself. Frankly, it'd be great >> if the JSP spec had a way to say "Look, every last page is going >> to be application/xml+html in UTF-8, unless I say otherwise, OK?" >> But it makes less sense for JSF to define this sort of thing on behalf >> of the JSP layer. HB> There is such a switch in JSP 2.0: you can use the <jsp-config> HB> element in web.xml to include a file that contains a page HB> directive with a contentType attribute in all or some pages.
        Hide
        Ed Burns added a comment -

        Sorry, this is the wrong issue. The issue I want is
        https://jsp-spec-public.dev.java.net/issues/show_bug.cgi?id=125

        Show
        Ed Burns added a comment - Sorry, this is the wrong issue. The issue I want is https://jsp-spec-public.dev.java.net/issues/show_bug.cgi?id=125

          People

          • Assignee:
            pierre
            Reporter:
            pierre
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: