Re: [sca-j] JAVA-98:Updated proposed resolution

[David Booz <booz@us.ibm.com>]

You're right! I'll raise an issue for the missing intent annotations. I hadn't realized that the Java specs were out of sync with the policy specs in terms of intents. A quick look shows clientAuthentication, serverAuthentication, and all the tran intents are missing. There's probably more....ugh.

Dave Booz
STSM, BPM and SCA Architecture
Co-Chair OASIS SCA-Policy TC and SCA-J TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093
e-mail:booz@us.ibm.com

Simon Nash ---04/24/2009 09:27:50 AM---David Booz wrote: > The problem with reviewing something over and over is that new

From:	Simon Nash <oasis@cjnash.com>
To:	sca-j@lists.oasis-open.org
Date:	04/24/2009 09:27 AM
Subject:	Re: [sca-j] JAVA-98:Updated proposed resolution

---

David Booz wrote:
> The problem with reviewing something over and over is that new 
> thoughts/issues come up every time you look at it.
> 
No problem, it happens to me all the time.

> 1) JCI spec - section 8 <service/> element generation (lines 376-391) - 
> I think some readers are going to ask, "What about annotations on the 
> interface class?" I'm thinking we should find a way to answer that 
> question with some text....maybe something along the lines of:
> Interfaces are not introspected but are considered during intent and 
> policySet processing as described in the Java CAA specification [ref] 
> and the Policy FW spec [ref].
> 
See new words in rev3 (just posted).

> 2) JCI spec - section 8.3 - Why repeat the managedTransaction intent 
> definition here?
> 
I don't think it's a repetition.  AFAIK, this specific intent
annotation is not defined by any SCA spec, so I defined it in the
example to make the example complete.

> 3) JCI spec - section 8.3 - Was it intentional on your part to NOT 
> implement MyService in MyServiceImpl
> 
Because there is an explicit @Service, it doesn't make any difference
whether or not there is a Java "implements" for this interface.
I didn't have any specific reason for omitting it.

   Simon

> no comments on JCAA spec.
> 
> Dave Booz
> STSM, BPM and SCA Architecture
> Co-Chair OASIS SCA-Policy TC and SCA-J TC
> "Distributed objects first, then world hunger"
> Poughkeepsie, NY (845)-435-6093 or 8-295-6093
> e-mail:booz@us.ibm.com
> 
> Inactive hide details for Simon Nash ---04/23/2009 11:19:48 AM---Here 
> are the revised versions of the Java CI and Java CAA docuSimon Nash 
> ---04/23/2009 11:19:48 AM---Here are the revised versions of the Java CI 
> and Java CAA documents with changes for JAVA-98, based
> 
> 
> From:		 
> Simon Nash <oasis@cjnash.com>
> 
> To:		 
> OASIS Java <sca-j@lists.oasis-open.org>
> 
> Date:		 
> 04/23/2009 11:19 AM
> 
> Subject:		 
> [sca-j] JAVA-98:Updated proposed resolution
> 
> ------------------------------------------------------------------------
> 
> 
> 
> Here are the revised versions of the Java CI and Java CAA documents with
> changes for JAVA-98, based on the discussion on Monday's call.
> 
> I also noticed that the introspection algorithm for @Service in section 8
> of Java CI didn't include the case of @Service specifying an implementation
> class, and I have corrected this.
> 
> http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/32216/sca-javacaa-1.1-spec-cd02-rev4%20issue98-rev2.doc
> http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/32214/sca-javaci-1.1-spec-wd07%20issue98-rev2.doc
> http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/32218/sca-javacaa-1.1-spec-cd02-rev4%20issue98-rev2.pdf
> http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/32215/sca-javaci-1.1-spec-wd07%20issue98-rev2.pdf
> 
>   Simon
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
> 
> 
> 



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php