IdP 3.4: Deprecated items in custom Syntax
Rod Widdowson
rdw at steadingsoftware.com
Tue Sep 26 06:17:32 EDT 2017
> We have experienced troubles about old format and new format of attribute-resolver.xml. For example, our example snippet in old
> format cannot apply to attribute-resolver.xml in 3.3.1.
That’s bad. Something which worked in V3.x *must* work for V3.y where x <= y. If that’s not the case Can you put in a JIRA case.
> Would all currently deprecated features (and possibly in future but before
> 4.0) be removed from 4.0?
It's best to assume this.
Things may change, but one of our motivations in 4.0 is to clear away a lot of deadwood which was put in V3.0 in order to support
the 2.x -> 3.0 transition but which is now confusing people and getting in the way of our future development.
It is an absolute aim for 3.4 (which we may or may not achieve) that we can guarantee that:
Any configuration which loads in V3.4 without warnings will load successfully in V4.0
I think we did a reasonably good job of the 2.0 -> 3.0 transition, but I want the 3.4 to 4.0 to be even easier (1->2 was hard 2->3
better I want 3->4 to be pain free).
Rod
More information about the dev
mailing list