I'm surprised this is not working. Also, you may have multiple methods for
the @SetupRender phase, but there are complications:
1) Parent class methods are invoked before child class methods
2) Methods within the same class are invoked in an odd order (alphabetical,
then by descending number of parameters for overrides of the same method
name)
3) If any method return non-void, later methods for the same phase are not
invoked
I'm sure some combination of the above rules is the explanation for why the
method is not being invoked.
On Wed, Nov 17, 2010 at 4:41 AM, nille hammer <
tapestry.nilleham...@winfonet.eu> wrote:
> Hi Stephan,
>
> sorry I did not realize that this was your workaround. To find a possible
> reason, I have experimented a bit changing return type, visibillity,
> parameter list of setupRender and even moved my component around different
> packages. I did not manage to setupRender not being called. Either it worked
> as expected or I got an Exception.
>
> The only way I managed a setupRender-Method not being called was having two
> of them in my component. Meaning I have one method following the naming
> convention and another one annotaded. It seems like the annotated one wins.
> You've said earlier that this is not the case for your component. So based
> on the current level of information I have no idea what could be the
> problem. I therefore kindly ask you to post full code (tml and java) of your
> component.
>
> Regards, nillehammer
>
> ----- original Nachricht --------
>
> Betreff: Re: Re: setupRender not called for components
> Gesendet: Mi, 17. Nov 2010
> Von: Stephan Windmüller<stephan.windmuel...@tu-dortmund.de>
>
> > On Wed, 17. Nov 2010, nille hammer wrote:
> >
> > > > | <t:if test="setupRender"/>
> > > > |
> > > > | public boolean isSetupRender() {
> > > > | // Do stuff
> > > > | return false;
> > > > | }
> > > I don't know whether this will solve your problem, but you don't need
> > > to put in an extra t:if to prevent your component from rendering. I
> > > suggest doing the checks in setupRender and return false, if you do
> > > not want anything rendered. Take a look at the rendering phases:
> > > http://tapestry.apache.org/tapestry5.1/guide/rendering.html
> >
> > You got me wrong. I am using this empty(!) tag and the method it calls
> > for doing the things I want to do in setupRender.
> >
> > As mentioned in my original e-mail, setupRender is not called.
> >
> > Regards
> > Stephan
> >
>
> --- original Nachricht Ende ----
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to learn
how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
