You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <de...@tuscany.apache.org> on 2009/07/30 18:39:14 UTC
[jira] Created: (TUSCANY-3187) Wires are associated with incorrect
service object
Wires are associated with incorrect service object
--------------------------------------------------
Key: TUSCANY-3187
URL: https://issues.apache.org/jira/browse/TUSCANY-3187
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-2.0
Environment: All
Reporter: Simon Laws
I came across this while running otest ASM_8002. I saw errors where it could do a class cast while trying to pass an OMElement into a service method that takes a string. Looking that this the wire between the Axis binding and the service doesn't have a databinding interceptor because both ends of the wire have Java interfaces.
It appears that in the promotion case the runtime wires on the service side are being associated with the wrong service. For example, where we have
composite
component1
service1 - binding.ws Endpoint1(references Component2 and Service2 as this is the true target for the endpoint)
implementation
service
component2
service2 - binding.sca = Endpoint2
implementation
When the Axis2ServiceProvider is created for Endpoint1 the provider is coded to retrieve the wire from service2. However we only store the wire for Endpoint1 on service1 at the moment.
Now this would be fine and easy to fix except that I chatted to Mike Edwards about this as he has been developing these tests and he doesn't see this error and is apparently on the same version of the code as me. So I'm checking in a fix to get us going but I'm nervous that something else is going on so am creating this JIRA and leaving it open to track the situation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-3187) Wires are associated with incorrect
service object
Posted by "Simon Laws (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Laws closed TUSCANY-3187.
-------------------------------
Resolution: Not A Problem
No longer applicable
> Wires are associated with incorrect service object
> --------------------------------------------------
>
> Key: TUSCANY-3187
> URL: https://issues.apache.org/jira/browse/TUSCANY-3187
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-2.0
> Environment: All
> Reporter: Simon Laws
> Assignee: Simon Laws
> Fix For: Java-SCA-Next
>
>
> I came across this while running otest ASM_8002. I saw errors where it could do a class cast while trying to pass an OMElement into a service method that takes a string. Looking that this the wire between the Axis binding and the service doesn't have a databinding interceptor because both ends of the wire have Java interfaces.
> It appears that in the promotion case the runtime wires on the service side are being associated with the wrong service. For example, where we have
> composite
> component1
> service1 - binding.ws Endpoint1(references Component2 and Service2 as this is the true target for the endpoint)
> implementation
> service
> component2
> service2 - binding.sca = Endpoint2
> implementation
> When the Axis2ServiceProvider is created for Endpoint1 the provider is coded to retrieve the wire from service2. However we only store the wire for Endpoint1 on service1 at the moment.
> Now this would be fine and easy to fix except that I chatted to Mike Edwards about this as he has been developing these tests and he doesn't see this error and is apparently on the same version of the code as me. So I'm checking in a fix to get us going but I'm nervous that something else is going on so am creating this JIRA and leaving it open to track the situation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-3187) Wires are associated with incorrect
service object
Posted by "Simon Laws (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Laws reassigned TUSCANY-3187:
-----------------------------------
Assignee: Simon Laws
> Wires are associated with incorrect service object
> --------------------------------------------------
>
> Key: TUSCANY-3187
> URL: https://issues.apache.org/jira/browse/TUSCANY-3187
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-2.0
> Environment: All
> Reporter: Simon Laws
> Assignee: Simon Laws
>
> I came across this while running otest ASM_8002. I saw errors where it could do a class cast while trying to pass an OMElement into a service method that takes a string. Looking that this the wire between the Axis binding and the service doesn't have a databinding interceptor because both ends of the wire have Java interfaces.
> It appears that in the promotion case the runtime wires on the service side are being associated with the wrong service. For example, where we have
> composite
> component1
> service1 - binding.ws Endpoint1(references Component2 and Service2 as this is the true target for the endpoint)
> implementation
> service
> component2
> service2 - binding.sca = Endpoint2
> implementation
> When the Axis2ServiceProvider is created for Endpoint1 the provider is coded to retrieve the wire from service2. However we only store the wire for Endpoint1 on service1 at the moment.
> Now this would be fine and easy to fix except that I chatted to Mike Edwards about this as he has been developing these tests and he doesn't see this error and is apparently on the same version of the code as me. So I'm checking in a fix to get us going but I'm nervous that something else is going on so am creating this JIRA and leaving it open to track the situation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-3187) Wires are associated with
incorrect service object
Posted by "ant elder (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737178#action_12737178 ]
ant elder commented on TUSCANY-3187:
------------------------------------
I see that on quite a few of the 5x tests, what is the easy fix you have?
> Wires are associated with incorrect service object
> --------------------------------------------------
>
> Key: TUSCANY-3187
> URL: https://issues.apache.org/jira/browse/TUSCANY-3187
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-2.0
> Environment: All
> Reporter: Simon Laws
> Assignee: Simon Laws
>
> I came across this while running otest ASM_8002. I saw errors where it could do a class cast while trying to pass an OMElement into a service method that takes a string. Looking that this the wire between the Axis binding and the service doesn't have a databinding interceptor because both ends of the wire have Java interfaces.
> It appears that in the promotion case the runtime wires on the service side are being associated with the wrong service. For example, where we have
> composite
> component1
> service1 - binding.ws Endpoint1(references Component2 and Service2 as this is the true target for the endpoint)
> implementation
> service
> component2
> service2 - binding.sca = Endpoint2
> implementation
> When the Axis2ServiceProvider is created for Endpoint1 the provider is coded to retrieve the wire from service2. However we only store the wire for Endpoint1 on service1 at the moment.
> Now this would be fine and easy to fix except that I chatted to Mike Edwards about this as he has been developing these tests and he doesn't see this error and is apparently on the same version of the code as me. So I'm checking in a fix to get us going but I'm nervous that something else is going on so am creating this JIRA and leaving it open to track the situation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.