[prev in list] [next in list] [prev in thread] [next in thread] 

List:       shibboleth-users
Subject:    RE: Namespace does not seem to include FilterElement
From:       "Rod Widdowson" <rdw () steadingsoftware ! com>
Date:       2016-03-31 14:28:08
Message-ID: 021e01d18b59$8e166e80$aa434b80$ () steadingsoftware ! com
[Download RAW message or body]

I just refreshed IDP-858 to refer to this

> -----Original Message-----
> From: users [mailto:users-bounces@shibboleth.net] On Behalf Of Cantor,
Scott
> Sent: 30 March 2016 15:11
> To: Shib Users
> Subject: Re: Namespace does not seem to include FilterElement
> 
> On 3/30/16, 10:08 AM, "users on behalf of Rod Widdowson" <users-
> bounces@shibboleth.net on behalf of rdw@steadingsoftware.com> wrote:
> 
> 
> 
> >> Well, we changed the names in some cases in the filter plugins.
> >
> >I'm quite happy to re-investigate this for 3.3 To my mind the namespace
> >flattening in the filters was one of the biggest ease of use wins in
3.2...
> 
> Well, for myself, I definitely would like to get rid of the namespaces,
but I think
> the big win in the resolver is the ordering mess.
> 
> I suspect the problem was that we were focusing on these two issues
> separately. If you don't change the namespaces, I think it's too hard to
fix the
> ordering "in place" in the schema, because the elements were spread across
> multiple namespaces. Fixing both at once should be very possible, because
the
> new xsi:types are fundamentally not the same types as before.
> 
> -- Scott
> 
> --
> To unsubscribe from this list send an email to users-
> unsubscribe@shibboleth.net

-- 
To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net
[prev in list] [next in list] [prev in thread] [next in thread]