[OASIS Issue Tracker] Issue Comment Edited: (SCAJ-15) Java EE Spec: Section 7.1.1 & 7.1.2 - should say that the EJB references are optionally made into SCA references

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/SCAJ-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29614#action_29614 ] 

Anish Karmarkar edited comment on SCAJ-15 at 2/28/12 6:25 PM:
--------------------------------------------------------------

This is OSOA JIRA issue 89

Original email at:
http://lists.oasis-open.org/archives/sca-j/200811/msg00001.html

Opened Nov 3 2008

re-opened Aug 21 2009 telecon

resolved Aug 21 2009 telecon - see minutes for text insertion locations

applied in WD06: http://www.oasis-open.org/committees/download.php/34200/sca-jee-1.1-spec-wd06.pdf


      was (Author: akarmark):
    Original email at:
http://lists.oasis-open.org/archives/sca-j/200811/msg00001.html

Opened Nov 3 2008

re-opened Aug 21 2009 telecon

resolved Aug 21 2009 telecon - see minutes for text insertion locations

applied in WD06: http://www.oasis-open.org/committees/download.php/34200/sca-jee-1.1-spec-wd06.pdf

  
> Java EE Spec: Section 7.1.1 & 7.1.2 - should say that the EJB references are optionally made into SCA references
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: SCAJ-15
>                 URL: http://tools.oasis-open.org/issues/browse/SCAJ-15
>             Project: OASIS Service Component Architecture / J (SCA-J) TC
>          Issue Type: Bug
>          Components: Java Common Annotations and APIs specification
>    Affects Versions: 1.1
>            Reporter: Anish Karmarkar
>             Fix For: 1.1
>
>
> Raiser: Mike Edwards
> Target: sca-jee-1[1][1].1-spec-wd04.doc
> Description:
> Section 7.1.1 & 7.1.2 - should say that the EJB references are optionally made into SCA references
> - as is stated in 7.1.3.
> This looks like a simple omission of intended normative statements from these sections.
> Proposal:
> Add the following text after line 914:
> In the absence of optional extensions, the component type of a non-SCA-enhanced EJB module
> does not contain SCA references. However, as an optional extension of the way in which SCA support
> is provided for EJB modules, an SCA runtime can choose to provide the capability of re-wiring
> EJB references using SCA. If an SCA runtime provides this optional extension, then the following
> rule is applied:
> Add the following text after the first sentence of line 952:
> In the absence of optional extensions, the component type of a non-SCA-enhanced Web module
> does not contain SCA references. However, as an optional extension of the way in which SCA support
> is provided for Web modules, an SCA runtime can choose to provide the capability of re-wiring
> EJB references using SCA. If an SCA runtime provides this optional extension, then the following
> rule is applied:

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira