[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: JAVA-21 - Clarify Request Scope lifetime
Hi, I’ve written the following proposal with the intent of
starting discussions on this issue before the next SCA-J Face to face. http://www.osoa.org/jira/browse/JAVA-21 From reading through the JIRA and mailing lists, there
appears to be different viewpoints on what Request Scope is for. These include:
All discussion on this issue stopped in March 2008. I would like to propose the following possible solutions
(personally, I prefer option 2) Option 1 - Remove Request Scope Simply remove it. Option 2 – Enhance the description of
Request Scope so it becomes a Shared Context for an invocation over a Remotable
interface The description of when the request scope ends it a bit
unclear since it does not detail what happens when the request goes through
another Remotable interface. I would like to propose the following guidelines:
Proposal: Original wording (section 2.2. lines 141 to 144): “The lifecycle of request
scope extends from the point a request on a remotable interface enters the SCA
runtime and a thread processes that request until the thread completes
synchronously processing the request. During that time, all service requests
are delegated to the same implementation instance of a request-scoped
component.” New wording – changes in bold: “The lifecycle of request
scope extends from the point a request on a remotable interface is made and a thread processes that request
until the thread completes synchronously processing the request. During that
time, all service requests that are over
local interfaces are delegated to the same implementation instance
of a request-scoped component. Any requests
that go over a Remotable interface will result in a new request scope being
created.” Thanks, Mark Mark Combellack| Software Developer| Avaya | |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]