You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Mike Edwards (JIRA)" <de...@tuscany.apache.org> on 2011/01/11 10:59:46 UTC
[jira] Created: (TUSCANY-3816) iTest Callback SeparateThread
violates the OASIS rules for COMPOSITE scope components with Callbacks
iTest Callback SeparateThread violates the OASIS rules for COMPOSITE scope components with Callbacks
----------------------------------------------------------------------------------------------------
Key: TUSCANY-3816
URL: https://issues.apache.org/jira/browse/TUSCANY-3816
Project: Tuscany
Issue Type: Bug
Components: Java SCA Integration Tests
Affects Versions: Java-SCA-2.0-M5
Reporter: Mike Edwards
Assignee: Mike Edwards
Fix For: Java-SCA-2.x
The iTest Callback SeparateThread has a component implementation EventProcessorServiceImpl.java which is @Scope("COMPOSITE") and which has a field annotated with @Callback.
This violates one of the conformance requirements of the OASIS Java CAA specification, which does not permit the use of the @Callback annotation for COMPOSITE scope components.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-3816) iTest Callback SeparateThread
violates the OASIS rules for COMPOSITE scope components with Callbacks
Posted by "Mike Edwards (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980033#action_12980033 ]
Mike Edwards commented on TUSCANY-3816:
---------------------------------------
The initial step is to disable this test from the build since the fix for the problem is not simple and will take some time to develop.
Committed in 1057555
> iTest Callback SeparateThread violates the OASIS rules for COMPOSITE scope components with Callbacks
> ----------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3816
> URL: https://issues.apache.org/jira/browse/TUSCANY-3816
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Integration Tests
> Affects Versions: Java-SCA-2.0-M5
> Reporter: Mike Edwards
> Assignee: Mike Edwards
> Fix For: Java-SCA-2.x
>
>
> The iTest Callback SeparateThread has a component implementation EventProcessorServiceImpl.java which is @Scope("COMPOSITE") and which has a field annotated with @Callback.
> This violates one of the conformance requirements of the OASIS Java CAA specification, which does not permit the use of the @Callback annotation for COMPOSITE scope components.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-3816) iTest Callback SeparateThread
violates the OASIS rules for COMPOSITE scope components with Callbacks
Posted by "Mike Edwards (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Edwards closed TUSCANY-3816.
---------------------------------
> iTest Callback SeparateThread violates the OASIS rules for COMPOSITE scope components with Callbacks
> ----------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3816
> URL: https://issues.apache.org/jira/browse/TUSCANY-3816
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Integration Tests
> Affects Versions: Java-SCA-2.0-M5
> Reporter: Mike Edwards
> Assignee: Mike Edwards
> Fix For: Java-SCA-2.x
>
>
> The iTest Callback SeparateThread has a component implementation EventProcessorServiceImpl.java which is @Scope("COMPOSITE") and which has a field annotated with @Callback.
> This violates one of the conformance requirements of the OASIS Java CAA specification, which does not permit the use of the @Callback annotation for COMPOSITE scope components.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (TUSCANY-3816) iTest Callback SeparateThread
violates the OASIS rules for COMPOSITE scope components with Callbacks
Posted by "Mike Edwards (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Edwards resolved TUSCANY-3816.
-----------------------------------
Resolution: Fixed
A basic fix to the test is committed in:
1058211
However, this test is not ideal in its current form - the COMPOSITE scope component makes the dangerous assumption that it has only 1 client and thus only 1 callback object. A real composite scoped component would have to allow for multiple clients - and would have to identify each of them separately via some kind of unique ID, which would ideally be described at the application level in the forward service interface to the component.
e.g.
String registerForEvent(String aEventName);
-- returns a registrationID as a String...
void unregisterForEvent(String aEventName, String registrationID);
-- cancels the registration for the given registrationID
> iTest Callback SeparateThread violates the OASIS rules for COMPOSITE scope components with Callbacks
> ----------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3816
> URL: https://issues.apache.org/jira/browse/TUSCANY-3816
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Integration Tests
> Affects Versions: Java-SCA-2.0-M5
> Reporter: Mike Edwards
> Assignee: Mike Edwards
> Fix For: Java-SCA-2.x
>
>
> The iTest Callback SeparateThread has a component implementation EventProcessorServiceImpl.java which is @Scope("COMPOSITE") and which has a field annotated with @Callback.
> This violates one of the conformance requirements of the OASIS Java CAA specification, which does not permit the use of the @Callback annotation for COMPOSITE scope components.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.