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!
This posed a big problem because major content rendering logic could be and
should be implemented in B.java.
I also found (but not tested yet) there is an API named data.setRedirectURI()
that might solve the problem. But I am not sure if $data is passed to the
called template correctly. Even if data.setRedirectURI() works fine in this
case, I still believe it is a major bug for data.setScreenTemplate skipping
doBuildTemplate of the called template.
Any solutions please?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
