on 6/17/01 6:01 PM, "a a" <[EMAIL PROTECTED]> wrote:
> Jon,
>
> I am using templating, my understanding is that
> Turbine looks up the corresponding layout vm from the
> screen vm filename. Please let me know if I am
> wrong...
Correct.
> Would the templating mechanism work in this case with
> subdirectories? E.g. screens/lang1/some_dir/index.vm
> gets the layout from layout/lang1/some_dir/index.vm?
Of course.
> You mentioned mod_webapp and mod_jk, which is a better
> solution? What are the advantages / disadvantages for
> both of them?
That is what you use to connect Tomcat to the HTTPd.
> Lastly, would you point me to some HOWTO style
> documents which would help me out?
Help you out with what?
> btw, I find two of the settings in config file
> Turbine.properties a bit confusing me...
>
> template.homepage/Index.vm
> template.login=/Login.vm
>
> So when a new request comes in from a client (not
> logged-in), which one gets loaded first?
It depends on what you have defined in your SessionValidator.
> My
> understanding is that template.homepage will be loaded
> first, and in the case of the sample app comes with
> Turbine, because the screen Index.class extends
> SecureScreens.class which does user authentication, it
> throws the user back to template.login, as the user
> has not logged-in. Correct me if I am wrong, I spent
> so much time on the docs and am still not 100% certain
> about the mechanism.
Again, it depends on the SessionValidator. You can also code this logic into
the Screen processing as well so that you can have some screens as being
"secure" and others as non-secure.
-jon
--
"Open source is not available to commercial companies."
-Steve Ballmer, CEO Microsoft
<http://www.suntimes.com/output/tech/cst-fin-micro01.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
