Hi Greg, This itest needs to be re-written after the changes to the PolicyHandling story for the java implementation extension.
Also I put in this itest to get some cases of policy annotations verified at a rudimentary level - like checking to see if the annotations ever get picked up and applied. IMO, using interceptors for this testing is quite ugly and not going to go very far. I am going to change this to explicitly execute read, resolve and build phases and simply verify against the built up composite. Thanks - Venkat On Mon, Apr 7, 2008 at 4:12 AM, Greg Dritschler <[EMAIL PROTECTED]> wrote: > What is the status of the policy itest? It uses the PolicyHandler > interface > to do its verification and that doesn't seem to work anymore, at least for > Java implementations. (The call to instantiate the > JavaPolicyHandlingRuntimeWireProcessor in JavaRuntimeModuleActivator is > commented out.) Is this itest going to be rewritten? > > I can't say that I understand how this itest was supposed to have worked. > The composite uses only one intent, TestIntent_3, on the implementation of > AddServiceComponent. That intent is provided by one policy set > TestPolicySet_3_implementation. Yet it looks to me like > TestImplPolicyHandler is quite happy if various other policy sets are > selected, such TestPolicySet_1_implementation or > TestPolicySet_2_implementation. What's the story? > > Greg Dritschler >
