You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Brent Daniel (JIRA)" <de...@tuscany.apache.org> on 2010/06/23 16:57:49 UTC

[jira] Commented: (TUSCANY-3606) POL_4007 Problems with mutually exclusive intent checking

    [ https://issues.apache.org/jira/browse/TUSCANY-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881710#action_12881710 ] 

Brent Daniel commented on TUSCANY-3606:
---------------------------------------

POL_4007 has been modified and is now passing, but the issue here still exists. 

> POL_4007 Problems with mutually exclusive intent checking
> ---------------------------------------------------------
>
>                 Key: TUSCANY-3606
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3606
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Policy
>            Reporter: Brent Daniel
>
> POL_4007 specifies two mutually exclusive intents at the Composite level. The intents are constrained to sca:binding, so we should only be checking for exclusivity at the binding level. Right now, we are checking (and failing) the intents in this test case at the Component level. 
> There is some code in ComponentPolicyBuilderImpl.removeConstrainedIntents() that attempts to remove  intents from any policy subject to which they do not apply. However, it does this based on the ExtensionType for the subject, which seems to be null for all SCA constructs other than bindings and implementations. It looks like it may be null for the default binding as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.