Is the reason is because a method named 'setupRender' takes on the same
actions as one annotated with @SetupRender and thus that method is called as
both a BeginRender and SetupRender method?
On 3/31/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
That is a tricky one; it should just be @BeginRender since you've gone
to the trouble of labelling it that way.
This is certainly a bug, but a low priority one, with an easy (but
very ugly) fix.
On 3/31/07, Sven Homburg <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> this sample would renderes two times in one cycle.
> it would be nice, if tapestry notice my error and show me a warning.
>
> public class Start
> {
> @BeginRender
> private void setupRender()
> {
> System.err.println("Hello from SetupRender");
> }
> }
>
> --
> Mit freundlichem Gruss
>
> homburg Softwaretechnik
> S.Homburg
> 21220 Seevetal / GERMANY
> Fon: +49-4105-669746
> Fax: +49-4105-668947
>
>
>
> ---------------------------------------------------------------------
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Peter Beshai
Computer Science Student
University of Waterloo
