[
https://issues.apache.org/jira/browse/TAPESTRY-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572995#action_12572995
]
Andreas Andreou commented on TAPESTRY-967:
------------------------------------------
>From a pragmatic POV, i don't see a value for this - it's easy to have
>specless components
and not deal with specifications at all...
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
