What I want to do now is display a different theme for different services.

Theme management is conveniently handled through the services management Web interface, /cas/services/manage.html. You specify the theme name there and must ensure that you have a corresponding Spring theme of that name on the classpath at deployment time.

If you intend on managing services via the services manager console in production, you should consider JpaTicketRegistry for production since the in-memory default implementation won't persist data across restarts.

Alternatively, manually adding services via bean definitions, as you did in your sample XML, should work, but you would not want to use the services manager console in that case. Maybe your experiment didn't work because your theme was missing from the classpath?

Finally, questions of this sort are best handled on the cas-user list.

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-dev

Reply via email to