-
15. Re: Policy Support in the Editor
bfitzpat Aug 28, 2012 4:30 PM (in response to bfitzpat)Ok, so I have two tabbed property pages working:
I still would like to know under what conditions these should appear. Currently they both appear anywhere we have a Contract object (composite service, composite reference, component service, component reference). It seems that we have partial support based on certain interfaces, implementations, and bindings. Can someone clearly explain which tabs should show up where?
Thanks!!
-
16. Re: Policy Support in the Editor
rcernich Aug 28, 2012 4:41 PM (in response to bfitzpat)Hey Brian,
Instead of a blank list entry, could we use something like "None" when no policy is specified (talking about the transaction policies).
Best,
Rob
-
17. Re: Policy Support in the Editor
bfitzpat Aug 28, 2012 5:03 PM (in response to rcernich)Yup. Can do that. Thanks!
-
-
19. Re: Policy Support in the Editor
kcbabo Aug 28, 2012 6:04 PM (in response to bfitzpat)I still would like to know under what conditions these should appear. Currently they both appear anywhere we have a Contract object (composite service, composite reference, component service, component reference). It seems that we have partial support based on certain interfaces, implementations, and bindings. Can someone clearly explain which tabs should show up where?
Turns out that it's not that straightforward. :-)
Implementation policy only applies to implementations, so you would only attach these on a service component (specifically, the implementation of a service component).
Interaction policy applies to a component-level service or reference.
Now that I've dropped the powder, here's the match that will make your head explode. The implementation policy is set once per implementation - so you wouldn't set this individually for a service or reference. The interaction policy can be set individually for the service and reference(s) on a component. This means that your tab view can still work, but the implementation policy will be the same for all service and reference definitions on the component. The nice thing is that you probably get this synchronization for free right now if you're using the EMF model - if you set the implementation value in the properties page of a service and then move to a reference on that component, the value read will be the same as the one set for the service.
Hopefully that makes a little bit of sense after the 10th read or so.
-
20. Re: Policy Support in the Editor
bfitzpat Aug 29, 2012 9:39 AM (in response to kcbabo)Thanks Keith. As I piece by brain pan back together and read it a few more times I think everything I need is in there... But wow. So much for consistency.