Unfortunately, I'm completely stalled by this weird template behavior and am
running out of time on my project.  If I cannot come up with some kind of fix I
will have to scrap Turbine and try to reuse some of my work with Velocity and
Torque unbundled from Turbine.  I was hoping someone has seen this error before
and can save me some extra work and delays.  It looks like this has been reported
before in the mailing list archives, but apparently there is no official "fix" for
this.

I tried some variations on my test case.  For instance, if the screen throws an
exception due to invalid data, then for some reason the 2nd time the template
(MyForm.vm) is rendered a different Screen is used (MyHome.java, the opening
screen) according to the Log output, but the template(MyForm.vm) gets displayed
with no data.   I still cannot imagine why in the world why doBuildTemplate() is
getting invoked a 2nd time!  Some kind of redirect is happening, perhaps, and the
parameters omitted from the URL, but what is causing this?

Nathaniel Reed wrote:

> I use
> <a href="$link.setPage("MyScreen.vm").addPathInfo("myParam",
> $myParamValue)">...</a>
>
> And this executes my screen (MyScreen), but according to the log output
> the screen gets executed a SECOND time without the parameters.. It fails
> (exception) this second time, and the screen gets output without the
> needed data.
>
> Any ideas?  Isn't this just bread-and-butter stuff?!  I'm not doing
> anything unusual here.
>
> --
> Nate Reed
> Physical Oceanography Distributed Active Archive Center
> Jet Propulsion Laboratory (Raytheon)
> [EMAIL PROTECTED]
> (626) 744-5528
> (626) 744-5506
>
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

--
Nate Reed
Physical Oceanography Distributed Active Archive Center
Jet Propulsion Laboratory (Raytheon)
[EMAIL PROTECTED]
(626) 744-5528
(626) 744-5506



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to