[TAP5-51] "Parents before Child" concept for Component Rendering does not allow different rendering in subclasses

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Assignee: Howard Lewis Ship
• Reporter: Fritz Pröbstle
• Created: 28/Mar/08 12:11
• Updated: 28/Sep/10 06:48
• Resolved: 30/Oct/08 21:45

Description

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 ?

Issue Links

• is related to: TAP5-1284 When using @PageActivationContext and override a no-args activate event handler of parent page, the handler called too soon