That's really, highly unlikely. I'd sprinkle in some extra text around the various components to confirm their render order. I really think you have some kind of unsaved file making it look like the componens render differently than they do.
On 5/30/07, Daniel Jue <[EMAIL PROTECTED]> wrote:
Hi, not sure if this is a problem or intended behavior: I have a <t:block> at the bottom of my template, but still inside the body. If I have this in a table, <td><t:selectsessionleveltype /><t:delegate to="typeOfSesionLevel" /></td> where typeOfSesionLevel returns a block, The block rendered by typeOfSesionLevel gets rendered before the component selectsessionleveltype. Of course I can force it to appear in the order I intended, but I could see this being an issue if, say, we were rendering bits and pieces of a large image using components and blocks. <td><t:selectsessionleveltype /></td> <td><t:delegate to="typeOfSesionLevel" /></td> Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com