ant elder wrote:
I can look at the existing specs and copy what they do for things like the SOAP intent or the JMS binding use of policy. I understand it can be useful to apply policy to a composite from out side but i disagree with you comment that anything else would "mess up the domain" and in this case where the alternative copies what an existing spec does and makes the simple case vastly simpler I think it may be better to do that or provide both options. ...ant
It doesn't look like we're reaching consensus on doing only one of the two options, maybe the consensus is to do both.
If you really want to do the 'binding attribute' option (which BTW should be in the Tuscany namespace I think) why don't you implement it?
I really want to see the 'policy set' option implemented, if you don't want to implement it I can spend the time to help implement it.
Both can coexist and will give Tuscany users two options to choose from, and we'll see over time what option they prefer in which configuration and circumstances.
Does that work? -- Jean-Sebastien --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
