> Currently we just parse the exception messages and throw new mapped > exceptions (similar to what Spring does with Oracle error codes -> data > access exceptions).
I'm thinking if we generalize that behavior into an interface, we can use it as a strategy to support both text parsing and ppolicy for generating exceptions. (The ppolicy response control is simply a BER-encoded object with details about account state, so it's nothing too onerous after you parse the BER.) > Something to work through via chat? Sure. If others are interested we can hash this out on #jasig-cas. You LPPE folks want to participate or listen in? 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
