RP config status

[Cantor, Scott]

On 5/29/14, 12:25 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
>
>It may be worth creating some shorthand constructors that auto-generate
>common predicates to use as conditions for the relying party definitions.
>The conditions are about the only inelegant syntax, so if we could smooth
>that over for some common cases, that would help.

This turns out to be pretty nice as a strategy because Spring does some
nice things when you use factory-methods to construct things. You can
still set properties that get set on the result of the factory-method, so
you can mix normal beans with a static helper class that builds the
objects in special ways.

So with a parent bean like this (hidden from the user):

<bean id="RelyingPartyByName" abstract="true"
  
class="net.shibboleth.idp.saml.relyingparty.impl.RelyingPartyConfigurationS
upport"
  factory-method="byName" ... />

The user just does this:


<bean parent="RelyingPartyByName"
	c:relyingPartyIds="#{{ 'https://sp.example.org',
'https://sp2.example.org' }}
	p:propertyToOverride="something">

That's fairly intuitive-looking all things considered.


Eventually you have to bail out to full bean definitions, but for anything
reasonably concise to capture in code, the predicates can be abstracted
into static methods and parent beans with built-in names, sort of like the
old custom xsi:types but without the XSD pain.

-- Scott