[jira] Updated: (TAPESTRY-967) SpecificationParser doesn't allow custom entities

["Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>]

     [ http://issues.apache.org/jira/browse/TAPESTRY-967?page=all ]

Jesse Kuhnert updated TAPESTRY-967:
-----------------------------------

    Fix Version/s: 4.1.1
                       (was: 4.1)

> SpecificationParser doesn't allow custom entities
> -------------------------------------------------
>
>                 Key: TAPESTRY-967
>                 URL: http://issues.apache.org/jira/browse/TAPESTRY-967
>             Project: Tapestry
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 4.0.1
>         Environment: all
>            Reporter: Marcus Schulte
>         Assigned To: Jesse Kuhnert
>            Priority: Minor
>             Fix For: 4.1.1
>
>         Attachments: tap_xml_entity_patch.txt
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org