[
https://issues.apache.org/jira/browse/TAPESTRY-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship updated TAPESTRY-889:
------------------------------------------
Affects Version/s: (was: 5.0)
4.2
> Components and pages cannot be overriden with ease (contrary to documentation)
> ------------------------------------------------------------------------------
>
> Key: TAPESTRY-889
> URL: https://issues.apache.org/jira/browse/TAPESTRY-889
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Affects Versions: 4.2
> Reporter: André
> Fix For: 4.2
>
>
> In
> http://jakarta.apache.org/tapestry/UsersGuide/components.html#components.libraries.namespace
> it is stated that components (from framework) can be overriden.
> "In fact, it is possible to override both pages and components provided by
> the framework. This is frequently used to change the look and feel of the
> default StateSession or Exception page. In theory, it is even possible to
> override fundamental components such as Insert or Foreach!"
> Why is it then not possible to override components within other namespaces?
> It is, for example, not possible just to override the contrib:TablePages
> component, while not touching the rest of contrib. There are several
> inelegant workarounds where you have to copy more or less of the component
> specs and templates.
> If Insert is overrideable, why not "namespace:Insert" for instance? This
> sound illogical to me and results in copy&paste'ing.
> Is this functionality important? To my opinion yes
> 1) It reduces code & configuration to maintain
> 2) It allows upgrading of single components within components without the
> need to touch the whole thing
> To solve this, it would be sufficient to allow overriding components in
> subsequent <library>ies.
> <library id="contrib"
> specification-path="/org/apache/tapestry/contrib/Contrib.library"/>
> <library id="contrib"
> specification-path="/org/my/own/tablePages/component/x.library"/>
> This currently results in an error message. "namespace already existent"
--
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]
