It looks like you would need one common JSP login page and just based on a request parameter, adjust the include.
This is my observation after a quick look at the APIs. There may be a better way.
-Scott
On 10/7/06, Peter Giesin <
[EMAIL PROTECTED]> wrote:
You say "parse that [service] and adjust what the ui looks like...".
Where is that being done? Is that in the JSP itself? If so that seems
a bit unwieldy. I woudl rather have separate JSPs, and then just load
the appropriate one.
Pete
On Oct 7, 2006, at 9:50 AM, Kevin Jordan wrote:
> I had to do the same thing. If you can base it on what the service
> they're being redirect to is, then just parse that and adjust what
> the ui looks like based on that.
>
> On 10/7/06, Peter Giesin < [EMAIL PROTECTED]> wrote: This may
> be more of a question for the Spring forum, but since I am
> asking in reference to CAS I figured I will ask it here. I have a
> requirement to have a unique login page for different services. I
> have tried to follow the logic through the ViewResolvers and
> Interceptors, but just can't seem to connect the dots. The thought
> was that there would be an extra parameter to the login service. This
> parameter could then be used to influence the return value from the
> ViewResolver, or something like that. Any suggestions would be very
> helpful.
>
> Thanks,
> Pete
> _______________________________________________
> Yale CAS mailing list
> [email protected]
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>
>
> --
> Kevin Jordan
> _______________________________________________
> 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
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
