OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-j message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [sca-j] NEW ISSUE: Problems with Example 2b in chapter 7 - [JAVA-129]


Sorry - forgot to put the issue number in the title. I have now
corrected this.

Thanks,

Mark

> -----Original Message-----
> From: Mark Combellack
> Sent: 09 February 2009 15:23
> To: 'Simon Nash'; OASIS Java
> Subject: RE: [sca-j] NEW ISSUE: Problems with Example 2b in chapter 7
> 
> Hi,
> 
> Raised as issue http://www.osoa.org/jira/browse/JAVA-129
> 
> Thanks,
> 
> Mark
> 
> > -----Original Message-----
> > From: Simon Nash [mailto:oasis@cjnash.com]
> > Sent: 09 February 2009 15:07
> > To: OASIS Java
> > Subject: [sca-j] NEW ISSUE: Problems with Example 2b in chapter 7
> >
> > TARGET: Java Common Annotations and APIs
> >
> > DESCRIPTION: Problems with Example 2b in chapter 7
> >
> > There are a number of problems with Example 2b in section 7.3.1
> > of cd02-rev2.
> >    a. The <service> definitions for HelloService and
HelloChildService
> >       should be inside the <component> definitions for
> >       HelloServiceComponent and HelloChildServiceComponent, not
> >       free-floating inside the <composite> definition.
> >    b. The <operation> definitions should not be within <component>
> >       defintions.  I believe the intention may have been to put them
> >       within <service> definitions.
> >    c. <operation> elements within <service> definitions were
> >       recently removed from the Assembly spec because of a decision
> >       by the Policy TC.
> >    d. The contents of the <operation> definitions don't seem
> >       consistent.  For the operations in HelloService, the
<operation>
> >       elements provide fully explicit definitions of the intents
that
> >       apply to the operations.  However, for the operations in
> >       HelloChildService, some of the <operation> elements only
provide
> >       partial definitions of the intents that apply.  Specifically,
> >         "hello" specifies "confidentiality/transport" but does not
> >            specify "authentication" and "integrity/transport".
> >         "helloWorld" specifies "authentication" but does not
> >            specify "integrity/transport" or
"confidentiality/message"
> >
> > PROPOSAL:
> >
> > Move the <service> definitions for HelloService and
HelloChildService
> > inside the <component> definitions for HelloServiceComponent and
> > HelloChildServiceComponent.
> >
> > Replace the <operation> definitions using the policy external
> > attachment mechanism to mark the operations with intents.
> >
> > Make the intent specifications on all the operations fully explicit.
> > Specifically, include the following explictly for HelloChildService:
> >   operation "hello":  "confidentiality/transport", "authentication"
and
> >                       "integrity/transport"
> >   operation "helloWorld":  "authentication", "integrity/transport"
and
> >                            "confidentiality/message"
> >
> >
> >
> >
---------------------------------------------------------------------
> > 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



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]