THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
The net result of associating intents and policysets with model elements is that computed policy sets are associated with bindings and/or implementations. The following is supported to date.
Current Policy Providers
o.a.t.s.policy.logging
Sample: samples/calculator-implementation-policies
...
The intent is read from the policy-logging definitions file
Each component is set up with all policy provider factories
During wire creation RuntimeWireImpl adds implementation interceptors and the policy provider factories for the component look at the component/operation to see if an interceptor is required
On invoke the logging takes place
o.a.t.s.policy.security.jaas
Sample: samples/calculator-implementation-policies
...
The intent is read from the policy-securitydefinitions file
Each component is set up with all policy provider factories
During wire creation RuntimeWireImpl adds implementation interceptors and the policy provider factories for the component look at the component/operation to see if an interceptor is required
On invoke the JAAS login is performed which relies on a set of Tuscany classes to authenticate the credentials returned from a callback?
The callack though has no message context from which to pull credentials?
Subject is not flowed through to the component
o.a.t.s.policy.security.ws
Sample: samples/helloworld-ws-service-secure
...
During Axis2ServicProvider.start() the policy handlers are first identified based on the computed policy sets and then the axis configuration is modified using these policy handlers.
o.a.t.s.policy.transaction (the policy implementation part)
TBD
...