Keith Seim <[EMAIL PROTECTED]> writes:
>Ok, this might be impossible, but I want to make use of the
>$link.setPage feature:
> $link.setPage("index.wm")
>... except I'd like to be able to put the Screen classname in there...
>for instance:
>$link.setPage("APP-NAME.modules.screens.Default") (where Default.class
>is the screen class I'm referring to).
$link.setPage -> sets the name of the Template to display
$link.setAction -> sets the Action parameter of a link
$link.setScreen -> sets the Screen parameter
So you should be able to do
<a href="$link.setScreen("Default").setTemplate("xxx.vm")">Next Screen</a>
to render the "Next Screen" with the xxx.vm Template and the Default Screen
class.
You don't have to give the fully qualified name, the Template Service
will look for it if you need this.
However, you can't change the screen class for the _current_
screen. Once the template gets prepared, you're already running the
java class for the current screen.
>Is that possible? I can't find this feature in the
>org.apache.turbine.*.*Link docs.
setScreen should've been always there. It definitely is in the 2.3-dev
code base in o.a.t.services.pull.tools.TemplateLink
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]
