|mrow...@bea.com||Jan 4, 2008 2:07 pm|
|Reza Shafii||Jan 4, 2008 2:19 pm||.xls|
|Mike Edwards||Jan 7, 2008 1:27 am|
|Simon Nash||Jan 7, 2008 4:58 am|
|David Booz||Jan 7, 2008 7:35 am|
|Reza Shafii||Jan 7, 2008 9:22 am|
|Blohm, Henning||Jan 7, 2008 9:43 am|
|Peshev, Peter||Jan 7, 2008 10:18 am|
|Simon Nash||Jan 7, 2008 11:01 am|
|Reza Shafii||Jan 7, 2008 1:06 pm||.xls|
|Simon Nash||Jan 7, 2008 3:43 pm||.xls|
|Mike Edwards||Jan 8, 2008 12:42 am|
|Blohm, Henning||Jan 8, 2008 12:49 am|
|Mike Edwards||Jan 8, 2008 12:50 am|
|Mike Edwards||Jan 8, 2008 1:32 am|
|Mike Edwards||Jan 8, 2008 2:22 am|
|Peshev, Peter||Jan 8, 2008 3:57 am|
|Mike Edwards||Jan 8, 2008 4:46 am|
|Simon Nash||Jan 8, 2008 5:51 am|
|Simon Nash||Jan 8, 2008 5:51 am|
|Reza Shafii||Jan 8, 2008 8:11 am|
|David Booz||Jan 8, 2008 8:31 am|
|Peshev, Peter||Jan 8, 2008 9:36 am|
|David Booz||Jan 8, 2008 12:46 pm|
|Reza Shafii||Jan 8, 2008 1:31 pm|
|Mike Edwards||Jan 9, 2008 2:45 am|
|Simon Nash||Jan 9, 2008 4:18 am|
|Mike Edwards||Jan 9, 2008 5:07 am|
|Mike Edwards||Jan 9, 2008 6:13 am|
|Michael Rowley||Jan 10, 2008 1:19 pm||.xls|
|Simon Nash||Jan 15, 2008 2:31 pm||.xls, .xls|
|Simon Nash||Jan 30, 2008 7:58 am||.xls, .xls|
|Mike Edwards||Jan 30, 2008 8:22 am||.xls, .xls|
|Subject:||RE: [sca-j] ISSUE 4 - Dependency reinjection|
|From:||Reza Shafii (rsha...@bea.com)|
|Date:||Jan 8, 2008 8:11:37 am|
Sorry for not being clear. I did not mean to imply that my suggestion was your proposoal. I was referring to your idea of annotation based reinjection while suggesting that we should stick to the previously discussed conditions for this to occur.
From: Mike Edwards [mailto:mike...@uk.ibm.com] Sent: Tue 08/01/2008 12:42 AM To: OASIS Java Subject: RE: [sca-j] ISSUE 4 - Dependency reinjection
I have one specific comment to make here - done inline....
Strategist - Emerging Technologies, SCA & SDO. Co Chair OASIS SCA Assembly TC. IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain. Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431 Email: mike...@uk.ibm.com
"Reza Shafii" <rsha...@bea.com> wrote on 07/01/2008 21:07:32:
Another option would be to use Mike's idea of a "reinject" parameter on @Reference to also derive the behavior of the getServiceReference() method. If reinject="true" reinjection should occur and subsequent invocations of getServiceReference() would lead to an object referencing the new target. If reinject="false", reinjection should not occur and subsequent invocations of getServiceReference() would lead to the target prior to rewiring.
I am also thinking that the reinject=true value would only be valid if the conditions previously discussed apply (i.e. scope is composite, conversational interfaces must not be active, and the reference is field based or setter based). This would change the table as attached.
This was NOT my proposal.
My proposal is that IF reinject=true is set, then reinjection occurs for ANY scope of component. My thinking here is that, since by default no reinjection occurs, and that the programmer has to do something active to get reinjection to occur, then it is reasonable to allow reinjection for any and all scopes - at the request of the programmer. This gets rid of those rules that you list above.
The thinking here is that IF you care about reinjection, then you will take the trouble to think through what it means to change the reference you are using (or perhaps, writers of material about SCA will take the trouble to tell you....).
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
Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.