You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org> on 2006/04/25 10:26:07 UTC
[jira] Created: (TUSCANY-224) ModuleContext locateService should
return a proxy if any interceptors are present in the invocation chain
ModuleContext locateService should return a proxy if any interceptors are present in the invocation chain
-----------------------------------------------------------------------------------------------------------
Key: TUSCANY-224
URL: http://issues.apache.org/jira/browse/TUSCANY-224
Project: Tuscany
Type: Bug
Components: Java SCA Core
Reporter: Jean-Sebastien Delfino
Priority: Blocker
ModuleContext.locateService always returns the target service instance, instead of returning a proxy configured with the invocation chain for the particular service. If there are any interceptors in the invocation chain, they will never be invoked.
This blocks development of any samples and test cases that use the SCA async PM from a simple client (JSP or J2SE client). Right now the helloworldasync sample must go through an intermediate component with a reference to the target service to be able to do any async invocation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (TUSCANY-224) ModuleContext locateService should
return a proxy if any interceptors are present in the invocation chain
Posted by "Jim Marino (JIRA)" <tu...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/TUSCANY-224?page=all ]
Jim Marino updated TUSCANY-224:
-------------------------------
Version: Mx
(was: M1)
Priority: Major (was: Blocker)
I took an detailed look at this and it is going to require changes in the core which I am working on. Once I have a better handle on these changes, we are going to need to decide whether to introduce them next week.
I am, however, lowering the priority of this since I don't think it is stop-ship and can be delayed to after M1. Also, there is a spec clarification that needs to be made when a service name is not provided.
Missing this feature will mean that we cannot show async from *non-managed* code but we can from managed code. Specifically, we can still demonstrate async from component to component; component to extenal service; and entry point to component.
> ModuleContext locateService should return a proxy if any interceptors are present in the invocation chain
> ---------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-224
> URL: http://issues.apache.org/jira/browse/TUSCANY-224
> Project: Tuscany
> Type: Bug
> Components: Java SCA Core
> Versions: Mx
> Reporter: Jean-Sebastien Delfino
> Assignee: Jim Marino
> Fix For: M1
>
> ModuleContext.locateService always returns the target service instance, instead of returning a proxy configured with the invocation chain for the particular service. If there are any interceptors in the invocation chain, they will never be invoked.
> This blocks development of any samples and test cases that use the SCA async PM from a simple client (JSP or J2SE client). Right now the helloworldasync sample must go through an intermediate component with a reference to the target service to be able to do any async invocation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (TUSCANY-224) ModuleContext locateService should
return a proxy if any interceptors are present in the invocation chain
Posted by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/TUSCANY-224?page=all ]
Jean-Sebastien Delfino reassigned TUSCANY-224:
----------------------------------------------
Assign To: Jim Marino
> ModuleContext locateService should return a proxy if any interceptors are present in the invocation chain
> ---------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-224
> URL: http://issues.apache.org/jira/browse/TUSCANY-224
> Project: Tuscany
> Type: Bug
> Components: Java SCA Core
> Versions: 0.91
> Reporter: Jean-Sebastien Delfino
> Assignee: Jim Marino
> Priority: Blocker
> Fix For: 0.91
>
> ModuleContext.locateService always returns the target service instance, instead of returning a proxy configured with the invocation chain for the particular service. If there are any interceptors in the invocation chain, they will never be invoked.
> This blocks development of any samples and test cases that use the SCA async PM from a simple client (JSP or J2SE client). Right now the helloworldasync sample must go through an intermediate component with a reference to the target service to be able to do any async invocation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (TUSCANY-224) ModuleContext locateService should
return a proxy if any interceptors are present in the invocation chain
Posted by "ant elder (JIRA)" <tu...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/TUSCANY-224?page=all ]
ant elder updated TUSCANY-224:
------------------------------
Fix Version: Java-Mx
(was: Java-M1)
> ModuleContext locateService should return a proxy if any interceptors are present in the invocation chain
> ---------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-224
> URL: http://issues.apache.org/jira/browse/TUSCANY-224
> Project: Tuscany
> Type: Bug
> Components: Java SCA Core
> Versions: Java-Mx
> Reporter: Jean-Sebastien Delfino
> Assignee: Jim Marino
> Fix For: Java-Mx
>
> ModuleContext.locateService always returns the target service instance, instead of returning a proxy configured with the invocation chain for the particular service. If there are any interceptors in the invocation chain, they will never be invoked.
> This blocks development of any samples and test cases that use the SCA async PM from a simple client (JSP or J2SE client). Right now the helloworldasync sample must go through an intermediate component with a reference to the target service to be able to do any async invocation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (TUSCANY-224) ModuleContext locateService should
return a proxy if any interceptors are present in the invocation chain
Posted by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Sebastien Delfino resolved TUSCANY-224.
--------------------------------------------
Resolution: Fixed
This is working on M2.
> ModuleContext locateService should return a proxy if any interceptors are present in the invocation chain
> ---------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-224
> URL: https://issues.apache.org/jira/browse/TUSCANY-224
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core
> Affects Versions: Java-Mx
> Reporter: Jean-Sebastien Delfino
> Assigned To: Jim Marino
> Fix For: Java-Mx
>
>
> ModuleContext.locateService always returns the target service instance, instead of returning a proxy configured with the invocation chain for the particular service. If there are any interceptors in the invocation chain, they will never be invoked.
> This blocks development of any samples and test cases that use the SCA async PM from a simple client (JSP or J2SE client). Right now the helloworldasync sample must go through an intermediate component with a reference to the target service to be able to do any async invocation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-224) ModuleContext locateService should
return a proxy if any interceptors are present in the invocation chain
Posted by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/TUSCANY-224?page=all ]
Jean-Sebastien Delfino updated TUSCANY-224:
-------------------------------------------
Fix Version: 0.91
Version: 0.91
> ModuleContext locateService should return a proxy if any interceptors are present in the invocation chain
> ---------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-224
> URL: http://issues.apache.org/jira/browse/TUSCANY-224
> Project: Tuscany
> Type: Bug
> Components: Java SCA Core
> Versions: 0.91
> Reporter: Jean-Sebastien Delfino
> Assignee: Jim Marino
> Priority: Blocker
> Fix For: 0.91
>
> ModuleContext.locateService always returns the target service instance, instead of returning a proxy configured with the invocation chain for the particular service. If there are any interceptors in the invocation chain, they will never be invoked.
> This blocks development of any samples and test cases that use the SCA async PM from a simple client (JSP or J2SE client). Right now the helloworldasync sample must go through an intermediate component with a reference to the target service to be able to do any async invocation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira