Uploaded image for project: 'Tapestry'
  1. Tapestry
  2. TAPESTRY-967

SpecificationParser doesn't allow custom entities

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • 4.0.1
    • 3.0.5, 4.2
    • Framework
    • None
    • all

    Description

      org.apache.tapestry.parse.SpecificationParser implements the method EntityResolver.resolveEntity() in a way that prohibits resolving any entities but the Tapestry specification DTD (it throws if the public-id does not equal either the 3.0 or the 4.0 spec).

      It would be useful to be able to refer to custom entities. That would allow one to include e.g. specs for base-class properties in all derived page-classes without having to repeat them (and without using annotations).

      suggested patch:
      in EntityResolver.resolveEntity() return null instead of throwing.

      Attachments

        1. tap_xml_entity_patch.txt
          6 kB
          Marcus Schulte

        Activity

          People

            jkuhnert Jesse Kuhnert
            mschu Marcus Schulte
            Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated: