Thanks, now it's clear to me. Multiple views are not really a need in my case. But they could be another way to solve my problem by creating different views for the different system loginpages which look like the original login pages. This would probably not be the best solution, but as the properties file is named "default_views.properties" and not "views.properties" I thought there could be a way to overrule those defaults. Therefore I just became curious about that.
Edi Scott Battaglia wrote: > I don't know where I put my code example. But simply put, the JavaScript is > needed to do a redirect (vs. using the normal HTTP 3xx redirect) because a > normal HTTP redirect will just perform the redirect in the IFRAME. Using > JavaScript, you can force the complete browser window to redirect. > > I'm curious, why do you need multiple views? > -Scott > > On 3/1/07, Edmund Mielach <[EMAIL PROTECTED]> wrote: > >> Thanks for your answers! >> I will also think about the traditional CAS redirect protocol. I would >> prefer this default way of using CAS, but some partners do have other >> preferences. Therefore I'm still curious about this iframe solution. I >> have tried to realize my loginpages in such a way before, but I didn't >> use JavaScript and had no success. I think I didn't quite catch the role >> of JavaScript in Scotts description of this solution. Does anyone have a >> code example or some additional information which enables me to >> understand it right? >> >> I was also wondering if it is possible to use multiple views. I only >> found the possibility to set a default view in default_views.properties. >> But is it possible to select an other view through a parameter at >> runtime or something like that? >> >> Edi >> _______________________________________________ >> Yale CAS mailing list >> [email protected] >> http://tp.its.yale.edu/mailman/listinfo/cas >> >> _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
