Sample Dataconnector for Shib 3.1

Krug, Jeff Jeff.Krug at gtri.gatech.edu
Mon May 11 14:01:17 EDT 2015


Does that mean I should not have a dependency on idp-attribute-resolver-spring?  Or that it's subject to change with 3.* release?  Or both?  

I had no dependencies on -impl libraries, but I did on that spring library and on net.shibboleth.ext.spring-extensions and net.shibboleth.utilities.java-support.

Thanks,
Jeff
 
________________________________________
From: dev <dev-bounces at shibboleth.net> on behalf of Cantor, Scott <cantor.2 at osu.edu>
Sent: Monday, May 11, 2015 1:49 PM
To: Shib Dev
Subject: Re: Sample Dataconnector for Shib 3.1

On 5/11/15, 1:42 PM, "Krug, Jeff" <Jeff.Krug at gtri.gatech.edu> wrote:
>
>My Parser was extending
>net.shibboleth.idp.attribute.resolver.spring.dc.AbstractDataConnectorParser​
>
>After 3.1, it seemed like that abstract class change changed and I had to change "doParse" to "doV2Parse" and I had to change "getBeanClass" to "getNativeBeanClass".

Not saying anything changed necessarily, but that's not API, so that could have changed. Yes, we need to get that documented.

>Certainly making sure I did not include any inappropriate dependencies in the pom file would be useful.

Anything -impl or -spring is *not* API. There are other specific cases that aren't that but are also not API (e.g. idp-consent isn't, idp-core is) so that's what we have to document.

-- Scott

--
To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net


More information about the dev mailing list