[
https://issues.apache.org/jira/browse/TUSCANY-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Dritschler updated TUSCANY-1765:
-------------------------------------
Attachment: TUSCANY-1765.patch
BaseJavaImplementationImpl.equals is modified to call its superclass
ComponentType.equals.
ComponentType.equals is modified to compare required intents.
> Component implementation has wrong intent
> -----------------------------------------
>
> Key: TUSCANY-1765
> URL: https://issues.apache.org/jira/browse/TUSCANY-1765
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Assembly Model
> Affects Versions: Java-SCA-0.99
> Reporter: Greg Dritschler
> Priority: Minor
> Attachments: TUSCANY-1765.patch
>
>
> Suppose there is a composite with multiple components that use the same
> implementation class but different implementation intents, as shown below.
> <composite xmlns="http://www.osoa.org/xmlns/sca/1.0"; name="CompositeX">
> <component name="ComponentA">
> <implementation.java class="test.DataServiceImpl"
> requires="managedTransaction.none"/>
> </component>
> <component name="ComponentB">
> <implementation.java class="test.DataServiceImpl"
> requires="managedTransaction.global"/>
> </component>
> </composite>
> In this case the components will share a common Implementation model object
> because only the class name is being used to determine whether a component's
> implementation is the same as another's. This means one of the components
> will have the wrong implementation intents recorded in the model.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
