net.shibboleth.idp.attribute.resolver.spring.dc has changed in IDP 3.2.x

[Joey Wang]

Thanks, Rod and Scott, for explanation.
My understanding of the project structure, according to this page, https://wiki.shibboleth.net/confluence/display/IDP30/ExtensionFundamentals is that developers like myself who are written extensions should not use any non-public classes. However, the extension guideline Rod wrote for attribute resolver (https://wiki.shibboleth.net/confluence/display/IDP30/3.+Developing+Attribute+Resolver+Extensions ) explicitly mentioned to extend AbstractDataConnectorParser. If this class is currently non-public in 3.2.x, are there other ways that I can write my attribute resolver extension without using it?
Also, contrary to what both of you stated in this thread, the document I cited above explicitly says all spring modules are public:
As the policy states, currently all of the code in the java-support and spring-extensions modules are part of the public API (by virtue of the fact that none of the packages at the time of authoring this page contain "impl" as a segment).    
Thanks, Joey

    On Friday, January 29, 2016 3:54 AM, Rod Widdowson <rdw at steadingsoftware.com> wrote:
 

 > I am a little confused with your following statement:

Scott explained it better than I.

> I believe it's being promoted into an API for a future release, and hasn't
been
> yet. I don't think it's there now. 

I was going to, and didn't because it is very tied in to two specific
parsers (LDAP and RDBMS), but I can certainly move it for in a later release
3.3 if there is sufficient need.  It sounds that with two requesters that
there is...

Rod

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


  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20160129/c630ef8d/attachment.html>