[
https://issues.apache.org/jira/browse/TAPESTRY-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship reassigned TAPESTRY-2311:
----------------------------------------------
Assignee: 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
> Assignee: Howard M. Lewis Ship
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
