Java F2F Meeting Minutes from Thursday 13th Morning

[Mike Edwards <mike_edwards@uk.ibm.com>]

Mark Combellack: Agenda:

9:00 to 9:15 Welcome
Appointment of scribe for day 3
Agenda bashing
Conference call on Monday 17th November

9:15 - 10:40 Concurrency
JAVA-61        Describe the concurrency model for each
scope
No proposal

JAVA-62        Clarify what a Component Implementation
can do with threads
Outline for proposal in Jira

JAVA-8          Concurrency model for Service
Reference instances
Proposal in Jira

JAVA-10        State sharing between ServiceReference
and type-safereference
Proposal in Jira

10:40 - 11:00 Break

11:00 - 12:45 Concurrency (continued)

12:45 - 1:45 Lunch

1:45 - 3:40 Component Type/unannotated POJOs
JAVA-55        SCA Java Specifications do not Adequately
Define the ComponentType of a Java implementation
Proposal in Jira

JAVA-17        A hole in the algorithm of introspecting
property/reference from an unannotated impl class
Proposal in Jira

JAVA-87        Java-related C&I specs needs to
define how effective CT is
No proposal


3:40 - 4:00 Break

4:00 - 6:00 Bindings/Interfaces
JAVA-77        A remotable service SHOULD be translatable
into a generally accepted standard for a service, such as WSDL 1.1 or WSDL
2.0
Proposal in Jira

JAVA-2          Determining the data binding to
use (e.g. JAXB or SDO)
No proposal

JAVA-7          Support for JAX-WS style async
methods
No proposal

JAVA-51        More examples on  mapping to Java
No proposal


6:00 Adjourn

Agenda Bashing:
replace items currently from 16:00 - 18:00 with a
consideration of Testing

Administrivia
Motion to cancel Java TC call on Monday 17th November
Proposed Martin, Ashok seconds
Accepted w/o

Motion to extend Monday TC calls to start 30 minutes
earlier
Proposed Dave B, seconded Mike E
Accepted w/o

"Concurrency" Section
JAVA-61        Describe the concurrency
model for each scope
http://www.osoa.org/jira/browse/JAVA-61
No proposal at present

1) Stateless Scope
Single threaded - the SCA runtime MUST ensure that an implementation instance
object is only ever dispatched on ONE thread at any one time. In addition,
within the SCA lifecycle of an instance, the SCA runtime MUST only make
a single invocation of one business method.  (NB the SCA lifecycle
might not correspond to the Java object lifecycle due to runtime techniques
such as pooling)
2) Composite Scope
Multi threaded - the SCA runtime MAY run multiple threads in a single implementation
instance object and it MUST NOT perform any synchronization
3) Conversation scope
Multi-threaded - the SCA runtime MAY run multiple threads in a single implementation
instance object and it MUST NOT perform any synchronization
Mike E moves to resolve Issue 61 with the wording
as above
Martin seconds
(Noting that editorial work will be required)
Accepted w/o - Issue 61 is resolved.

Mark Combellack: Breaking - resuming at 10:50
GMT
JAVA-62        Clarify what a
Component Implementation can do with threads
Outline for proposal in Jira
http://www.osoa.org/jira/browse/JAVA-62

Simon Nash: http://gee.cs.oswego.edu/dl/concurrencyee-interest/index.html
Direction #1
Need to create a series of statements relating to
the implementation code containing "SHOULD" and "SHOULD
NOT" clauses
Need to  create a corresponding series of statements
relating to the SCA runtime containing "MAY" clauses concerning
what the runtime might do if an implementation chooses to use/abuse threading
capabilities
eg:
A stateless scope implementation SHOULD NOT attempt
to start, stop, suspend, or resume a thread, or to change a thread's priority
or name.
Direction #2
Need to create a controlled set of facilities for
SCA implementations to use in the areas of Work management and Timers,
parallel to the specification of JSR 236
eg: An SCA runtime MAY refuse to provide any runtime
facilities for a thread that it does not create/control (eg refuse to allow
invocation of service reference methods)
Action: (Mark C) Draw up some wording for Direction
1 and publish to the list
Action: (Mark C + others prepared to help) Investigate
the Workmanager JEE spec and determine its applicability to SCA

JAVA-8          Concurrency
model for Service Reference instances
Proposal in Jira
http://www.osoa.org/jira/browse/JAVA-8
The real problem here is mutability of service references
- associated with Callbacks and Conversations
If the mutability is removed, then Issue 8 gets resolved
very simply
This depends on the resolution of some other issues
As a result, cannot progress this issue at this time

JAVA-10        State sharing between
ServiceReference and type-safereference
Proposal in Jira
http://www.osoa.org/jira/browse/JAVA-10
Again, this depoends on the question of mutability
of service references
Direction for resolution:
IF mutability of references is removed (Issue 95)
THEN the need for ServiceReference is removed - and by making reference
proxies guaranteed to be serializable, all necessary function is present.
Make Issue 10 dependent on the resolution of Issue
95

Mark Combellack: Breaking for lunch - resuming
at 1:10 GMT

         
      
Yours,  Mike.

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_edwards@uk.ibm.com

---

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