[cas-dev] ServiceRegistry Bean

[Tillinghast, Andrew P.]

This is something of aesthetic opinion but now that the default in memory ServiceRegistry Bean is more involved I'd like to suggest that it should be removed from deployerConfigContext.xml and instead be placed in a separate serviceRegistry.xml configuration file under spring configuration.  By definition: deployerConfigContext.xml centralizes into one file some of the declarative configuration that all CAS deployers will need to modify. Speaking with other CAS deployers I don't really get a strong impression that Service registry is modified frequently and if it is, then it's usually replaced by JPA solution. Andrew Tillinghast Sr. Web Developer atill...@conncoll.edu 270 Mohegan Avenue New London, CT 06320-4196 Ph:860 439-5265 Fax: 860 439-2871 P Think before you print CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system. -- 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