CAS 3.1.1 with GlassFish v2 (b58g)

[Tim Kettering]

Hi - its me again.

Updating the JSP file (WEB-INF/view/jsp/default/ui/casLoginView.jsp)  
with the solution suggested in the first link mentioned in the  
previous email.  (adding action="?" to the form tag) so it looks like  
the below:

update form:form tag to:
<form:form method="post" id="fm1" cssClass="fm-v clearfix"  
commandName="${commandName}" htmlEscape="true" action="?">

will enable it to work properly in glassfish v2

-tim


On Nov 12, 2007, at 4:47 PM, Tim Kettering wrote:

>
> Ok a bit of googling turned up the following discussion links.   
> Seems to be a bug with Glassfish when using the spring forms tag.
>
> http://weblogs.java.net/blog/johnsmart/archive/2007/07/spring_mvc_tile.html
>
> http://forum.springframework.org/archive/index.php/index.php/t-37761.html
>
> -tim
>
> On Nov 12, 2007, at 4:15 PM, Tim Kettering wrote:
>
>>
>> I can also confirm that CAS 3.1.1 deployed straight up to Glassfish  
>> (V2) does not work for some reason.   A older application based on  
>> 3.0.6 works just fine.
>>
>> I'm going to dig around a bit.. but yeah.. it seems borked.
>>
>> -tim
>>
>> On Nov 5, 2007, at 8:43 AM, Scott Battaglia wrote:
>>
>>> 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 <santtu.vuori at comptel.com> 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
>>> cas at tp.its.yale.edu
>>> http://tp.its.yale.edu/mailman/listinfo/cas
>>>
>>>
>>>
>>> -- 
>>> -Scott Battaglia
>>>
>>> LinkedIn: http://www.linkedin.com/in/scottbattaglia  
>>> _______________________________________________
>>> Yale CAS mailing list
>>> cas at tp.its.yale.edu
>>> http://tp.its.yale.edu/mailman/listinfo/cas
>>
>> _______________________________________________
>> Yale CAS mailing list
>> cas at tp.its.yale.edu
>> http://tp.its.yale.edu/mailman/listinfo/cas
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20071112/4a4fba82/attachment.html