You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org> on 2007/06/20 17:58:27 UTC
[jira] Updated: (TAPESTRY-967) SpecificationParser doesn't allow
custom entities
[ https://issues.apache.org/jira/browse/TAPESTRY-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Kuhnert updated TAPESTRY-967:
-----------------------------------
Fix Version/s: 4.2
> SpecificationParser doesn't allow custom entities
> -------------------------------------------------
>
> Key: TAPESTRY-967
> URL: https://issues.apache.org/jira/browse/TAPESTRY-967
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Affects Versions: 4.0.1
> Environment: all
> Reporter: Marcus Schulte
> Assignee: Jesse Kuhnert
> Priority: Minor
> Fix For: 3.0.5, 4.2
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org