tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davor Hrg (JIRA)" <...@tapestry.apache.org>
Subject [jira] Created: (TAPESTRY-2252) Support for EmbededComponent as Block without template tag
Date Wed, 12 Mar 2008 13:32:47 GMT
Support for EmbededComponent as Block without template tag

                 Key: TAPESTRY-2252
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2252
             Project: Tapestry
          Issue Type: Improvement
    Affects Versions: 5.0.12
            Reporter: Davor Hrg
            Priority: Minor
             Fix For: unspecified

I have a complex form with multiple steps,

I've embeded the parts so I can notify them to reset state when new entity is loaded...
but beside that it looks like this:

    @Component private Eri _eri;
    @Component private Route _route;
    @Component private Barges _barges;
    @Component private Consigments _consigments;
    @Component private Containers _containers;
    @Component private Finish _finish;

and in the template I need:
	<t:block t:id="eri_block"          ><p t:id="eri"/></t:block>
	<t:block t:id="route_block"        ><p t:id="route"/></t:block>
	<t:block t:id="barges_block"       ><p t:id="barges"/></t:block>
	<t:block t:id="consigments_block"  ><p t:id="consigments"/></t:block>
	<t:block t:id="containers_block"   ><p t:id="containers"/></t:block>
    <t:block t:id="finish_block"       ><p t:id="finish"/></t:block>

It is not that much, but I'd prefer to not have to write the above code into template,
there could be a parameter to mark the embeded component as a block
so the framework is strict about this and to avoid problems with misspelled ids.
something like this:
    @Component(block=true) private Finish _finish;
    @Component @Block private Finish _finish;

all these component need not render them selves, but will be included as 
block inside a t:delegate, so their position in template is irrellevant.

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

View raw message