Function use in the IdP

Rod Widdowson rdw at steadingsoftware.com
Wed Nov 12 04:09:23 EST 2014


> I'm more in favor I think of having an alternate constructor, 

Makes sense.

> Or are you suggesting we modify the existing
> function code to check the type and walk the tree as needed to get to the
> PRC?
 
No, my reasoning is that if all I can configure is a
Function<ProfileContext, Whatever> and what I happen to need is a
Function<MumbleContext, Whatever> then I should be able to construct, in
Spring, a composite function made up of a [series of] functions to go from
MumbleContext to ProfileContext composed with the Scripted Function.

This presupposes that (a) the navigation between contexts is config time
fixed and that (b) we already have Functions which span all the potential
navigations.  I know that we have Parent and Child and also something to
provide IncomingMessage and OutgoingMessage.  I assume that we have
something to go from incoming or outgoing from the MessageContext to the
PRC.  Are there any other navigation options missing? It would be the work
of minutes to add a ScriptedFunction<Object,ProfileContext>, just in case.

/Rod




More information about the dev mailing list