Thanks Marvin. That clarifies the issue. The master branch does not register the JsonExceptionResolver for the webapp and that's correct. That particular resolver was moved over to the management webapp, since it was primarily responsible for handling ajax errors that may occur as part of the services management's D&D functionality. Removing the bean config renders the "CAS is unavailable" message which is the correct and desired behavior.
I have just pushed my changes over here with json resolver removed: https://github.com/mmoayyed/cas/tree/CAS-1251-35x If you get a chance, would you mind testing the changes once more to confirm? Thanks, -Misagh > -----Original Message----- > From: Marvin Addison [mailto:marvin.addi...@gmail.com] > Sent: Friday, February 08, 2013 10:45 AM > To: cas-dev@lists.jasig.org > Subject: Re: [cas-dev] 3.5.2 > > The behavior I'm seeing is what I would expect. You've registered two > HandlerExceptionResolver components: > > 1. > org.springframework.web.servlet.view.json.exception.JsonExceptionResolv > er > (applicationContext.xml) > 2. org.jasig.cas.web.FlowExecutionExceptionResolver (cas-servlet.xml) > > When BadlyFormattedFlowExecutionKeyException is raised, #2 returns null > which signals the next handler (JsonExceptionResolver) to handle it. > The fact that you see JSON-formatted text is evidence, and stepping > through in a debugger confirms this explanation. > > What I can't explain is why you're _not_ seeing this in the master > branch. Spring versions are different, but it's hard to imagine that > would explain it. > > M > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > mmoay...@unicon.net To unsubscribe, change settings or access archives, > see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
