You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2008/08/19 19:13:45 UTC

[jira] Updated: (TAPESTRY-2311) "Parents before Child" concept for Component Rendering does not allow different rendering in subclasses

     [ https://issues.apache.org/jira/browse/TAPESTRY-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAPESTRY-2311:
-------------------------------------------

    Assignee:     (was: Howard M. Lewis Ship)

> "Parents before Child" concept for Component Rendering does not allow different rendering in subclasses
> -------------------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-2311
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2311
>             Project: Tapestry
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.0.11
>            Reporter: Fritz Pröbstle
>             Fix For: 5.0.13
>
>
> I   subclassed  GridPager ( public class MyGridPager extends GridPager) to implement another pager visualisation.
> After creating a MyGrid (public class MyGrid extends Grid) which uses MyGridPager and copying Grid,tml to MyGrig.tml ist was ready to test.
> Start.tml:
>         <t:mygrid source="tl" row="treffer" rowsPerPage="5">
>                <t:parameter name="regnrcell">
>                  <t:pagelink page="marke2"  >	${treffer.regnr}</t:pagelink>
>             </t:parameter> 
>         </t:mygrid>
> It runs fine - but I got the "old" ,default Visualiation *AND* the   new one.  It is a result of the "Parents before Child" concept .
> First the Parent creates its visualisatrion the my Child createy its new visualisation.
> Subclasses can not decide of they want to call the implemetation of their parent or not.
> Why is this implemented like this?
> Why call parent implemtation at all, the child could do this explicit by calling super.XXX.( I know Annotations may make this more complex)
> Can you help ?

-- 
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