Details

    • Issuezilla Id:
      489
    • Status Whiteboard:
      Hide

      size_large importance_medium

      Show
      size_large importance_medium

      Description

      Standard and custom tags should be described using XML Schema, not another
      proprietary tag descriptor language (TLD). Nearly every XML editor on the planet
      understands, supports, and can provide tag completion with documentation for the
      XML document when an XML Schema is associated with it.

      XML Schema also has the most advanced facility for describing the valid syntax
      for an element or attribute (permitted child elements, presence of EL
      expressions, etc). By standardizing on XML Schema, which itself is a W3C
      standard, developers don't have to wait for vendors to create tooling for basic
      XML editing capabilities. Also, developers have become very used to XML schema
      with it being supported in the Seam component and pages descriptor and Spring
      and Spring Web Flow configuration files.

      In summary, importing a custom tag into a view template would involve defining
      an XML namespace and optionally (though preferably) associating that namespace
      with an XML schema document. Component libraries would be required to provide
      this XML Schema document (perhaps generated; and yes, it is worth doing!).

        Activity

        Hide
        Ed Burns added a comment -

        Move to unscheduled target milestone

        Show
        Ed Burns added a comment - Move to unscheduled target milestone
        Hide
        Ed Burns added a comment -

        Prepare to delete "spec" subcomponent.

        Show
        Ed Burns added a comment - Prepare to delete "spec" subcomponent.
        Hide
        mojavelinux added a comment -

        Update target milestone to 2.1

        Show
        mojavelinux added a comment - Update target milestone to 2.1
        Hide
        Ed Burns added a comment -

        I agree with this. But it's not a P1

        Show
        Ed Burns added a comment - I agree with this. But it's not a P1
        Hide
        rogerk added a comment -

        triage

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

        edburns

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

        Change target milestone.

        Show
        Ed Burns added a comment - Change target milestone.
        Hide
        Ed Burns added a comment -

        I discussed this on IRC with Andy Schwartz today. We have some basic questions. I looked Dan's blog
        entry http://in.relation.to/Bloggers/ItsTimeForFaceletsToStartUsingXSD and even in his attachment the
        .xsd files do not have enough information for the runtime to wire up the components to the renderers, and
        whatever other taglib metadata we need.

        Moving to P3

        Show
        Ed Burns added a comment - I discussed this on IRC with Andy Schwartz today. We have some basic questions. I looked Dan's blog entry http://in.relation.to/Bloggers/ItsTimeForFaceletsToStartUsingXSD and even in his attachment the .xsd files do not have enough information for the runtime to wire up the components to the renderers, and whatever other taglib metadata we need. Moving to P3
        Hide
        rogerk added a comment -

        triage

        Show
        rogerk added a comment - triage

          People

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

            Dates

            • Created:
              Updated:
              Resolved: