Hi, I agree to your views on intents and I also like the proposal you are making with respect to making use of 'appliesTo'. Sounds like a clean way out.
The only issue standing in the way is of how we get hold of the SCDL over which the xpath in 'appliesTo' can be applied. I'd like to use our assembly model writers to write back an SCA artifact (component or service ... ) as XML and then apply the xpath in appliesTo over this XML. All this must be done in the policyset matching phase. However, matching of policysets happen in the Builders which is in the assembly module and referring back to the assembly-xml for the writers causes a cyclic dependency. Will moving the builders out to a separate module like assembly-builder be a good way out. Or, is there any other better way of getting hold of the SCDL or accessing the assembly model writers ? Thanks - Venkat On Jan 25, 2008 9:52 AM, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > Venkata Krishnan wrote: > >> - Why did you need two authentication and wsAuthentication intents? is > >> it because you needed different policy sets on the client and service > >> side? > >> > > > > Yes, that's the reason. Since the policysets encapsulate things like > the > > username, password callback hander etc. which could be different for the > > client and the server there needed to be different policysets. Having > the > > same intent does no guarantee that the right policyset will be matched > i.e. > > the client's policyset for the reference and the server's policyset for > the > > service. Having unique intents will ensure this mapping. > > After looking at this again today I think that having different custom > authentication intents defeats the purpose of intents, turning them into > disguised policySets as they become specific to the particular config of > authentication in parts of your network. > > We need a different approach: > - keep intents abstract (authentication) > - declare where different policySets providing authentication should be > applied in the composition. > > PolicySet/appliesTo already provides a way to scope the application of a > policySet. Can we just use that? > > Some examples: > appliesTo="binding.ws" > appliesTo="[EMAIL PROTECTED]'AccountService']" > appliesTo="../[EMAIL PROTECTED]'AccountServiceComponent']" > > Thoughts? > -- > Jean-Sebastien > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
