RE: [sca-j] NEW ISSUE: When is a RequestContext available?

[Simon Nash <NASH@uk.ibm.com>]

Sanjay,
Here's my terminology model:
A component is a configuration of an implementation.
There can (in general) be many instances of an implementation.  Each of 
these instances is configured by the component.
Invocations to a component (via a service) are dispatched to an instance 
of the component
In the above, I said "...instance of the component" rather than 
"...instance of the implementation" because the instance has had the 
component's configuration applied to it

Is there an SCA glossary somewhere that provides approved definitions of 
the above terms?

    Simon

Simon C. Nash, IBM Distinguished Engineer
Member of the IBM Academy of Technology
Tel. +44-1962-815156  Fax +44-1962-818999



"Patil, Sanjay" <sanjay.patil@sap.com> 
30/01/2008 18:12

To
Simon Nash/UK/IBM@IBMGB, <sca-j@lists.oasis-open.org>
cc

Subject
RE: [sca-j] NEW ISSUE: When is a RequestContext available?







Just a nitpick -  You have used the term 'an instance of the component'
a few times below. I would have thought that a component itself is an
instance (of an implementation). Perhaps replacing 'an instance of the
component' with 'the component instance' would be more appropriate!

Regarding the issue and the proposal - both make sense to me.

-- Sanjay

> -----Original Message-----
> From: Simon Nash [mailto:NASH@uk.ibm.com] 
> Sent: Wednesday, Jan 30, 2008 6:11 AM
> To: sca-j@lists.oasis-open.org
> Subject: [sca-j] NEW ISSUE: When is a RequestContext available?
> 
> RAISER: Simon Nash
> 
> TARGET: SCA Java Annotations and APIs Section 7.1: ComponentContext
> 
> DESCRIPTION:
> 
> The decription of ComponentContext.getRequestContext() says in lines 
> 647-648 that it returns null if "... there is no current 
> request or if the 
> context is unavailable".  The situations where this applies 
> need to be 
> defined more precisely.  Here are some cases where a request 
> context may 
> or not be available:
> 1. Within a business method for a service of the component.
> 2. Within a property or reference injection setter method for 
> an instance 
> of the component.
> 3. Within a constructor for an instance of the component.
> 4. Within an Init or Destroy method for an instance of the component. 
> 
> In case 1, it seems clear that getRequestContext() will always return 
> non-null.  In the other cases, it is not clear what should be 
> returned.
> 
> PROPOSAL:
> 
> getRequestContext() MUST return non-null for case 1 and 
> SHOULD return null 
> for cases 2 through 4.
> 
> 
> Simon C. Nash, IBM Distinguished Engineer
> Member of the IBM Academy of Technology
> Tel. +44-1962-815156  Fax +44-1962-818999
> 
> 
> 
> 
> 
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales 
> with number 
> 741598. 
> Registered office: PO Box 41, North Harbour, Portsmouth, 
> Hampshire PO6 3AU
> 
> 
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all 
> your TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgr
> oups.php 
> 
> 







Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU