The commandName has nothing to do with the actual url. CommandName is a
Spring construct.
If I can get a chance I'll download GlassFish and try it out. If you can
open a JIRA issue to track this (in case there is a problem), that would be
great.
Thanks
-Scott
On 11/5/07, Santtu Vuori <[EMAIL PROTECTED]> wrote:
>
> Hi!
>
> I downloaded the CAS 3.1.1 server package, deployed the war file on Tomcat
> 6.0.14 and it works. I am however more interested in running the
> application on
> GlassFish and I've noticed that it doesn't work.
>
> On the casLoginView.jsp (the default view) the commandName has a wrong
> value -
> the actual value might have been lost already earlier....?
>
> <form:form method="post" id="fm1" cssClass="fm-v clearfix"
> commandName="${commandName}" htmlEscape="true">
>
> On Tomcat the commandName is "/cas/login?null" but on GF the commandName
> translates to "/cas/WEB-INF/view/jsp/default/ui/casLoginView.jsp?null"
> which
> doesn't naturally work.
>
> I will replace the view code with my own customised version and I can even
> hard
> code the actual commandName, but I think the question is why doesn't this
> work
> with GF? Is there something that CAS/Spring/Spring WebFlow expects from
> the web
> container or depends on.... like ThreadLocals?
>
> Has anyone been able to deploy CAS 3.1.1 server on GF successfully -
> out-of-the-box, without customising any parts of the application?
>
> BR,
> /Santtu
>
> _______________________________________________
> Yale CAS mailing list
> [email protected]
> http://tp.its.yale.edu/mailman/listinfo/cas
>
--
-Scott Battaglia
LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
