Marvin,
I did some debugging on my end and I found that if I remove spring:theme tags  
from /src/main/webapp/WEB-INF/view/jsp/default/ui/includes/top.jsp and hard 
code css links instead, the CAS login page starts  rendering inside the 
portlet, no errors. There is something wrong with the theme resolver, I think.


Kostya


-----Original Message-----
From: Marvin S. Addison [mailto:[email protected]] 
Sent: Thursday, May 31, 2012 3:56 PM
To: [email protected]
Subject: Re: [cas-user] NullPointerException in ServiceThemeResolver or not? 
CAS 3.4.7

> 2012-05-31 10:51:23,077 ERROR 
> [org.springframework.web.servlet.tags.ThemeTag] -<null> 
> java.lang.NullPointerException
>                  at java.util.regex.Matcher.getTextLength(Unknown Source)
>                  at java.util.regex.Matcher.reset(Unknown Source)
>                  at java.util.regex.Matcher.<init>(Unknown Source)
>                  at java.util.regex.Pattern.matcher(Unknown Source)
>                  at 
> org.jasig.cas.services.web.ServiceThemeResolver.resolveThemeName_aroundBody0(ServiceThemeResolver.java:54)
>                  at 
> org.jasig.cas.services.web.ServiceThemeResolver.resolveThemeName_aroundBody1$advice(ServiceThemeResolver.java:44)
>                  at 
> org.jasig.cas.services.web.ServiceThemeResolver.resolveThemeName(ServiceThemeResolver.java:1)
>                  at 
> org.springframework.web.servlet.support.RequestContextUtils.getTheme(RequestContextUtils.java:147)
>                  at 
> org.springframework.web.servlet.support.RequestContext.getTheme(RequestContext.java:328)
>                  at 
> org.springframework.web.servlet.tags.ThemeTag.getMessageSource(ThemeTag.java:50)
>                  at 
> org.springframework.web.servlet.tags.MessageTag.resolveMessage(MessageTag.java:193)
>                  at 
> org.springframework.web.servlet.tags.MessageTag.doStartTagInternal(MessageTag.java:165)
>                  at 
> org.springframework.web.servlet.tags.RequestContextAwareTag.doStartTag(RequestContextAwareTag.java:79)
>                  at 
> org.apache.jsp.WEB_002dINF.view.jsp.errors_jsp._jspx_meth_spring_005ft
> heme_005f0(errors_jsp.java:169)

Hey Kostya.  Sure looks like the same stack trace as that cited in CAS-952, but 
I can't imagine why you'd get this if you're running a version where that issue 
is fixed.  I'll have to do some code review before I can comment further, which 
I'll hopefully get to in the next few days.  If anyone has any other ideas in 
the interim, please speak up.

M

--
You are currently subscribed to [email protected] as: 
[email protected] To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

-- 
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

Reply via email to