You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Scott Kurz (JIRA)" <tu...@ws.apache.org> on 2007/02/28 18:09:56 UTC
[jira] Created: (TUSCANY-1146) ServiceContract clone() doesn't
clone Operations()
ServiceContract clone() doesn't clone Operations()
--------------------------------------------------
Key: TUSCANY-1146
URL: https://issues.apache.org/jira/browse/TUSCANY-1146
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core
Affects Versions: Java-M2
Reporter: Scott Kurz
Fix For: Java-SCA-integration
ServiceContract.clone() does:
if (operations != null) {
Map<String, Operation<T>> clonedOperations = new HashMap<String, Operation<T>>();
for (Operation<T> o : operations.values()) {
clonedOperations.put(o.getName(), o);
}
copy.setOperations(clonedOperations);
}
This is going to interfere with the 'operations' of the original ServiceContract (since setOperations points the Operations to the new SC). We should have cloned the operations I believe.
--
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-1146) ServiceContract clone() doesn't
clone operations
Posted by "Scott Kurz (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Kurz updated TUSCANY-1146:
--------------------------------
Attachment: 1146.patch
Same patch with ASF license..sorry
> ServiceContract clone() doesn't clone operations
> ------------------------------------------------
>
> Key: TUSCANY-1146
> URL: https://issues.apache.org/jira/browse/TUSCANY-1146
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core
> Affects Versions: Java-M2
> Reporter: Scott Kurz
> Fix For: Java-SCA-integration
>
> Attachments: 1146.patch, 1146.patch
>
>
> ServiceContract.clone() does:
> if (operations != null) {
> Map<String, Operation<T>> clonedOperations = new HashMap<String, Operation<T>>();
> for (Operation<T> o : operations.values()) {
> clonedOperations.put(o.getName(), o);
> }
> copy.setOperations(clonedOperations);
> }
> This is going to interfere with the 'operations' of the original ServiceContract (since setOperations points the Operations to the new SC). We should have cloned the operations I believe.
--
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-1146) ServiceContract clone() doesn't
clone operation
Posted by "Scott Kurz (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Kurz updated TUSCANY-1146:
--------------------------------
Summary: ServiceContract clone() doesn't clone operation (was: ServiceContract clone() doesn't clone Operations())
> ServiceContract clone() doesn't clone operation
> -----------------------------------------------
>
> Key: TUSCANY-1146
> URL: https://issues.apache.org/jira/browse/TUSCANY-1146
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core
> Affects Versions: Java-M2
> Reporter: Scott Kurz
> Fix For: Java-SCA-integration
>
>
> ServiceContract.clone() does:
> if (operations != null) {
> Map<String, Operation<T>> clonedOperations = new HashMap<String, Operation<T>>();
> for (Operation<T> o : operations.values()) {
> clonedOperations.put(o.getName(), o);
> }
> copy.setOperations(clonedOperations);
> }
> This is going to interfere with the 'operations' of the original ServiceContract (since setOperations points the Operations to the new SC). We should have cloned the operations I believe.
--
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-1146) ServiceContract clone() doesn't
clone operations
Posted by "Scott Kurz (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Kurz updated TUSCANY-1146:
--------------------------------
Attachment: 1146.patch
This is a patch on the integration-branch. (Should I have attached one to the trunk as well? )
> ServiceContract clone() doesn't clone operations
> ------------------------------------------------
>
> Key: TUSCANY-1146
> URL: https://issues.apache.org/jira/browse/TUSCANY-1146
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core
> Affects Versions: Java-M2
> Reporter: Scott Kurz
> Fix For: Java-SCA-integration
>
> Attachments: 1146.patch
>
>
> ServiceContract.clone() does:
> if (operations != null) {
> Map<String, Operation<T>> clonedOperations = new HashMap<String, Operation<T>>();
> for (Operation<T> o : operations.values()) {
> clonedOperations.put(o.getName(), o);
> }
> copy.setOperations(clonedOperations);
> }
> This is going to interfere with the 'operations' of the original ServiceContract (since setOperations points the Operations to the new SC). We should have cloned the operations I believe.
--
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Resolved: (TUSCANY-1146) ServiceContract clone() doesn't
clone operations
Posted by "Raymond Feng (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raymond Feng resolved TUSCANY-1146.
-----------------------------------
Resolution: Fixed
Fix Version/s: Java-SCA-M3
Thanks for the patch.
I have applied to both trunk and sca-java-integration branch.
http://svn.apache.org/viewvc?view=rev&rev=512871
http://svn.apache.org/viewvc?view=rev&rev=512883
> ServiceContract clone() doesn't clone operations
> ------------------------------------------------
>
> Key: TUSCANY-1146
> URL: https://issues.apache.org/jira/browse/TUSCANY-1146
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core
> Affects Versions: Java-M2
> Reporter: Scott Kurz
> Assigned To: Raymond Feng
> Fix For: Java-SCA-M3, Java-SCA-integration
>
> Attachments: 1146.patch, 1146.patch
>
>
> ServiceContract.clone() does:
> if (operations != null) {
> Map<String, Operation<T>> clonedOperations = new HashMap<String, Operation<T>>();
> for (Operation<T> o : operations.values()) {
> clonedOperations.put(o.getName(), o);
> }
> copy.setOperations(clonedOperations);
> }
> This is going to interfere with the 'operations' of the original ServiceContract (since setOperations points the Operations to the new SC). We should have cloned the operations I believe.
--
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-1146) ServiceContract clone() doesn't
clone operations
Posted by "Scott Kurz (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Kurz updated TUSCANY-1146:
--------------------------------
Summary: ServiceContract clone() doesn't clone operations (was: ServiceContract clone() doesn't clone operation)
> ServiceContract clone() doesn't clone operations
> ------------------------------------------------
>
> Key: TUSCANY-1146
> URL: https://issues.apache.org/jira/browse/TUSCANY-1146
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core
> Affects Versions: Java-M2
> Reporter: Scott Kurz
> Fix For: Java-SCA-integration
>
>
> ServiceContract.clone() does:
> if (operations != null) {
> Map<String, Operation<T>> clonedOperations = new HashMap<String, Operation<T>>();
> for (Operation<T> o : operations.values()) {
> clonedOperations.put(o.getName(), o);
> }
> copy.setOperations(clonedOperations);
> }
> This is going to interfere with the 'operations' of the original ServiceContract (since setOperations points the Operations to the new SC). We should have cloned the operations I believe.
--
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Assigned: (TUSCANY-1146) ServiceContract clone() doesn't
clone operations
Posted by "Raymond Feng (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raymond Feng reassigned TUSCANY-1146:
-------------------------------------
Assignee: Raymond Feng
> ServiceContract clone() doesn't clone operations
> ------------------------------------------------
>
> Key: TUSCANY-1146
> URL: https://issues.apache.org/jira/browse/TUSCANY-1146
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core
> Affects Versions: Java-M2
> Reporter: Scott Kurz
> Assigned To: Raymond Feng
> Fix For: Java-SCA-integration
>
> Attachments: 1146.patch, 1146.patch
>
>
> ServiceContract.clone() does:
> if (operations != null) {
> Map<String, Operation<T>> clonedOperations = new HashMap<String, Operation<T>>();
> for (Operation<T> o : operations.values()) {
> clonedOperations.put(o.getName(), o);
> }
> copy.setOperations(clonedOperations);
> }
> This is going to interfere with the 'operations' of the original ServiceContract (since setOperations points the Operations to the new SC). We should have cloned the operations I believe.
--
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org