[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [sca-j] Handling the remaining open issues and our first Public Review - Updated plan
Hi, [I have updated this plan based on the
comments from the meeting and the updated issue statuses] I have been looking through the 21
remaining open issues that we have for the SCA-J specification and I am very
aware that we need to have a Public Review Draft very soon. Currently, I feel
that we will not be able to resolve all the 21 open issues before we go to
Public Review. Currently we have told the Liaison committee that we will not
reach the original mid-March date and are now aiming to go for Public Review in
mid-April To this end, as chairs we feel that as a
TC, we should: ·
Schedule
some more conference call times (will cover this in a separate discussion) ·
Concentrate
on what must be resolved before going to Public Review. I have been through all of the open issues
and prioritized them so we can focus our efforts with the remaining time. Below, I have listed the remaining open
issues: List A:
Issues that must resolve before Public Review These issues must be resolved before going
to Public Review. JAVA-104 RFC2119
Language is needed for CAA Specification JAVA-105 RFC2119
Language is needed for C&I Specification JAVA-119 JAA
Conformance Section List B:
Issues that would be nice to resolve before Public Review It would be nice if the following issues
were resolved before going to Public Review. However, if they are not resolved,
then they are not critical enough to prevent the Public Review from taking
place. JAVA-123 Java
C&I - Remove references to conversational function JAVA-129 Problems
with Example 2b in chapter 7 JAVA-65 There
is no lifecycle defined for SCA Components List C:
Issues that we could leave unresolved until after Public Review The following issues can remain unresolved
when going to Public Review. This list has been split into two groups, namely
those issues that have a proposal and could be resolved in 10 minutes (referred
to as 10 minute issues) and those that cannot. Starting from Monday 16th March
up to the Public Review, I will focus the scheduled call time on the issues
from List A and List B. However, 10 minute issues from List C may be considered
for discussion if no progress can be made or there is insufficient time left on
the to make progress on the on issues from List A and List B. Issues with proposals
that could be resolved in 10 minutes – 10 Minute Issues JAVA-125 Allow
call semantics to be specified in interface.java JAVA-134 @Callback
and @Remotable on implementation classes Issues with proposals
that could be left unresolved JAVA-127 Long
running request/response operations JAVA-131 @Callback
injection could be NULL (expanded to include refs, property and re-injection
and callback ctor injection) JAVA-98 Can
annotations be inherited JAVA-1 Accessing
SCA Services from non-SCA component code JAVA-46 equals()
method on ServiceReference and CallableReference JAVA-139 Default
value for SCA property is not supported for java implementations JAVA-62 Clarify
what a Component Implementation can do with threads JAVA-78 Need
API to set EPR and for a reference invocation JAVA-51 More
examples on <interface.wsdl> mapping to Java JAVA-54 Section
7.1 of the Java CAA Specification is unclear JAVA-53 what
happens if init() throws a runtime exception (Blocked by JAVA-65) JAVA-13 ComponentContext.getProperty(...)
ill defined (Blocked by JAVA-139) In addition to the above issues, we need
to ensure that Test Assertions and Test Cases are written. There is currently
no issue open for this task. I have tried to be as harsh as possible
with the above lists. Most of the nice to resolve issues are
“editorial” stuff to correct examples and clarify existing
functionality. Generally the issues in the defer list are new features or
enhancements to the current specification. I expect there may be some
disagreement with my classifications but feel free to raise any strong
disagreements that you may have. I would also like to encourage people to
focus their attention on the issues in List A and List B. This will maximise
our ability to resolve as many of the pressing issues before we go to Public
Review. Thanks, Mark Mark Combellack| Software Developer| Avaya | |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]