It's good to know that. But the caveat is still a result of bad design. The
template and associated class are supposed to have a more tight bond. What I
recommend is adopting Microsoft .Net's strategy: to create a class out of the
the template A.vm (using similar technology of jsp), and let this class derive
from A.java.
Fred
Quoting "Henning P. Schmiedehausen" <[EMAIL PROTECTED]>:
> [EMAIL PROTECTED] writes:
>
> >If there is a class (say A.java) associated with a Velocity template (A.vm),
>
> >the class will be called first to bild template if A.vm is requested in URL.
>
> >What I found out in Turbine 2.2.1 TDK is that if I redirect to another
> template
> >(B.vm) in an Action or a template class (A.java) by calling
> >data.setScreenTemplate("B.vm"), then B.vm's associated class (B.java) is not
>
> >called!
>
> If you do this in an Action, it is. If you do this in a screen class,
> it is not.
>
> Once you're in the screen class (A.java) and you change the Template,
> the engine that matches a class to your template already ran and gave
> you a result (A.java), the class that you're currently running. :-)
>
> If you do this in an action, then this engine is just about to be
> run. So it should work.
>
> Regards
> Henning
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
> [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
>
> Java, perl, Solaris, Linux, xSP Consulting, Web Services
> freelance consultant -- Jakarta Turbine Development -- hero for hire
>
> --- Quote of the week: "It is pointless to tell people anything when
> you know that they won't process the message." --- Jonathan Revusky
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
