I'm open to not using OpenSAML. I'll take a look at your branch/pull request ASAP.
On Fri, Feb 20, 2015 at 9:41 AM, Marvin Addison <marvin.addi...@gmail.com> wrote: > I've been doing a fair bit of client-side CAS work lately, and it's become > apparent that OpenSAML is a huge integration pain when integrating the > client into non-trivial Java webapps. Dragging in dependencies as diverse > as joda-time, velocity, and copious XML libraries is the first and biggest > pain. Beyond that, it's a large, complex library that is a poor fit for our > simple processing needs. We went that route because we had encountered some > problems with XML namespace handling, but in retrospect we should have > simply tightened up on the XML processing. While I wish I could go back in > history and choose that path from the start, I would argue that it's not > too late to go there. I've got a working XPath-based processing solution on > the following branch: > > https://github.com/Jasig/java-cas-client/tree/no-opensaml > > While I think XPath-processing could benefit the CAS protocol components > down the road, the present work only touches SAML and support components. > (One small exception: I removed an XML parser configuration parameter that > is no longer relevant.) I would appreciate review and feedback. While I'm > committed to this solution regardless because of an internal project, I'd > like to submit a pull request to master since I think it's generally > beneficial. > > M > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > scott.battag...@gmail.com > 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
