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: Raw chat log of 2009-03-02 telcon


anish: 0. Administration
- Issue Status: Open: 29
- Daylight saving starts March 8 in the US - calls will be an hour 
earlier for those in Europe from 9th March for 3 weeks


1. Review action items:

Action Items that I believe are done:

Action Items that I believe are still to be done:
2008-07-15-02: Dave to produce a proposal for JAVA-2
2008-11-11-22: Mark to draw up some wording for Direction 1 (as 
discussed at the November F2F) for JAVA-62
2008-11-11-23: Mark (and others prepared to help) to investigate the 
WorkManager JEE spec and determine its applicability to SCA for JAVA-62
2009-02-13-01: Mike to upload artifacts for JAVA-121 into OASIS Open SVN
2009-02-13-02: Chairs to look at how the files for JAVA-121 should be 
licensed
2009-02-16-01: Mike to fix the usage of "class loader" through out the spec
2009-02-19-02: Mark to update proposal for JAVA-65 to remove @PostInit 
and @PreDestroy.
2009-02-23-01: Anish to write proposal for JAVA-119
2009-02-23-02: Mike to provide proposal for JAVA-54
2009-03-23-03: Editors to make sure org.osoa replaced with org.oasisopen
2009-02-23-05: Simon to try and create alternate example for JAVA-129
2009-02-23-06: Simon to write proposal for Java 131


2. Blocking issues

a. JAVA-105: RFC2119 Language is needed for C&I Specification
http://www.osoa.org/jira/browse/JAVA-105
Proposal (PDF): 
http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/31463/sca-javaci-1.1-spec-wd04_proposal.pdf 

Proposal (Word): 
http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/31464/sca-javaci-1.1-spec-wd04_proposal.doc 


The other 2 blocking issues are waiting for updated proposals.


3. Critical Issue discussion

a. JAVA-1: Accessing SCA Services from non-SCA component code
http://www.osoa.org/jira/browse/JAVA-1
Proposal: http://lists.oasis-open.org/archives/sca-j/200901/msg00094.html
Updated code proposal: 
http://lists.oasis-open.org/archives/sca-j/200902/msg00225.html

The other critical issue is waiting for an updated proposal.


4. New Issues

None


5. Other Open Issues discussion

a. JAVA-13: ComponentContext.getProperty(...) ill defined
http://www.osoa.org/jira/browse/JAVA-13
proposal: http://lists.oasis-open.org/archives/sca-j/200902/msg00179.html

b. JAVA-74: Clarify meaning of "should implement"
http://www.osoa.org/jira/browse/JAVA-74
Proposal: http://lists.oasis-open.org/archives/sca-j/200902/msg00186.html

c. JAVA-136: Remove the use of componentType side files from the Java 
C&I specification
http://www.osoa.org/jira/browse/JAVA-136
Proposal in Jira

d. JAVA-97: no ability to attach different intents /PolicySets to 
different services
http://www.osoa.org/jira/browse/JAVA-97
Proposal: http://lists.oasis-open.org/archives/sca-j/200902/msg00187.html

e. JAVA-98: Can annotations be inherited
http://www.osoa.org/jira/browse/JAVA-98
Outline Proposal: 
http://lists.oasis-open.org/archives/sca-j/200902/msg00192.html

f. 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
http://www.osoa.org/jira/browse/JAVA-77
Updated proposal: 
http://lists.oasis-open.org/archives/sca-j/200902/msg00166.html

g. JAVA-133: Unannotated properties and references
http://www.osoa.org/jira/browse/JAVA-133
Proposal: In Jira

h. JAVA-135: Problems with definition of @Service annotation
http://www.osoa.org/jira/browse/JAVA-135
Proposal: In Jira

i. JAVA-102 - Need to have a Name parameter on the @Service annotation
http://www.osoa.org/jira/browse/JAVA-102
Updated proposal: 
http://lists.oasis-open.org/archives/sca-j/200902/msg00222.html

j. JAVA-137: Java C&I Constructor Examples are incorrect
http://www.osoa.org/jira/browse/JAVA-137
Proposal in Jira


6. Blocking issues waiting for updates/proposals

a. JAVA-104: RFC2119 Language is needed for CAA Specification
http://www.osoa.org/jira/browse/JAVA-104
Proposal: http://lists.oasis-open.org/archives/sca-j/200902/msg00201.html
Waiting for email feedback and resulting updates

b. JAVA-119: JAA Conformance Section
http://www.osoa.org/jira/browse/JAVA-119
Updated proposal: 
http://lists.oasis-open.org/archives/sca-j/200902/msg00021.html
Alternative proposal: 
http://lists.oasis-open.org/archives/sca-j/200902/msg00049.html
Waiting for email discussion and new proposal


7. Critical issues waiting for updates/proposals

a. JAVA-54: Section 7.1 of the Java CAA Specification is unclear
http://www.osoa.org/jira/browse/JAVA-54
No proposal


8. AOB


---------------------------------------------------------------
Rotating scribe list:

Peter Walker Sun Microsystems (1)
Roberto Chinnici Sun Microsystems (2)
Peter Peshev SAP AG (2)
Ron Barack SAP AG (3)
Michael Beisiegel IBM (3)
Sanjay Patil SAP AG (3)
Vladimir Savchenko SAP AG (1)
Jim Marino Individual (4)
Pradeep Simha TIBCO Software Inc. (5)
Vamsavardhana Chillakuru IBM (3)
Plamen Pavlov SAP AG (2)
Graham Charters IBM (1)
Martin Chapman Oracle Corporation (6)
Yang Lei (4)
Mike Edwards IBM (7)
Meeraj Kunnumpurath Individual (3)
Anish Karmarkar Oracle Corporation (8 )
Bryan Aupperle IBM (7)
Ashok Malhotra Oracle Corporation (7)
Simon Nash Individual (5)

jeff.mischkinsky: (Autoreply) sleeping -- zzzzzzzzz - dreaming of IM's

anonymous morphed into Graham Charters

Ashok: running a bit late ... will join in a few minutes

Mike Edwards: are you able to dial in Vamsi?

Vamsi: I just got in

Dave Booz: scribe: Dave Booz

Dave Booz: meeting is quorate

Dave Booz: topic: agenda

Dave Booz: no changes

Dave Booz: topic: approval of minutes

Dave Booz: no objections to approving the minutes

Dave Booz: topic: Issue status - 29 open

Dave Booz: topic: TC administrivia

Dave Booz: Mark remonds everyone about the daylight savings changes in 
the US starting next week

Dave Booz: topic: Action Items

Dave Booz: no changes to what is posted in the agenda

Dave Booz: topic: blocking issues

Dave Booz: http://www.osoa.org/jira/browse/JAVA-105

Dave Booz: Mike E walks us through the proposal form the agenda

Dave Booz: s/form/from

Dave Booz: 
http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/31463/sca-javaci-1.1-spec-wd04_proposal.pdf

Please change your name from 'anonymous' using the Settings button

anish dave, almost there

anish dave, i can take over, thx

anish: Scribe: Anish Karmarkar

anish: ScribeNick: anish

anish: Date: 2009-03-02

anish: SimonN: the MUST in section 8 overlaps with the one in section 8.3

anish: ... surprised that there is only one error case

Mark Combellack lowered your hand

anish: Anish: why not have a statement about errors in section 8 as a 
catch all

Mark Combellack lowered your hand

anish: ... we'll have more errors in the future, so best to future proof 
it by the catch all

anish: SimonN: found a note in section 8 that talks about name attribute 
on ref being required (constructor param)

anish: MikeE: that is a note as the reuqirement is stated in the 
annotation section

anish: ... but you have pointed out that there is word 'required' that 
needs to be changed

anish: ... (line 370)

anish: ... similarly there is one in the properties section

anish: MikeE/SimonN: such errors should be in CAA

anish: Bryan: in line 542 there is a 'required' that is a keyword

anish: Bryan: during the CAA spec discussion about keyword we said that 
'which APIs should be implemented would go in C&I', I didn't see that

Mark Combellack lowered your hand

anish: MikeE: 2 changes, 665 and 672 needs to be normative

anish: SimonN: Q about section 9, can you have '.' in NCName

anish: Ashok: yes

anish: MikeE: for chapter 11, there may be more needed, just converted 
what was there

anish: ... we should consider other stmts separately

anish: SimonN: we need a statement about implementation.java schema

anish: Mark: sounds like a new issue

anish: MikeE: we should handle all of section 11 as a separate issue 
like the other specs

anish: SimonN: 1st line of Appendix B -- s/Assembly/JavaC&I/

anish: SimonN: comment on section 5, the 3 bullets at the beginning 
should be normative

anish: SimonN: will do my thorough review later

anish: MikeE: i have more homework to do

anish: Topic: other 2 blocking issues

jeff.mischkinsky: test

anish: Mark: we do have proposal on CAA from MikeE, we'll see that next time

anish: Topic: Issue Java-1

anish: JAVA-1: Accessing SCA Services from non-SCA component code
http://www.osoa.org/jira/browse/JAVA-1
Proposal: http://lists.oasis-open.org/archives/sca-j/200901/msg00094.html
Updated code proposal: 
http://lists.oasis-open.org/archives/sca-j/200902/msg00225.html

anish: Mark goes through his updated proposal

anish: MikeE: u have default ClientFactoryFounder, but it is not 
callable by default

anish: Mark: we provide a ref implementation for the Finder

anish: s/Founder/Finder/

anish: ... vendor don't have to provide an impl of SCAClientFactory but 
do have to provide an impl of ClientFactoryFinder

anish: SimonN: havent' looked at the src code yet, but otherwise looks fine

anish: MikeE: you have various test stuff, can you explain that

anish: ... what are you trying to show with vendor1, vendor2 impl

anish: Mark: just different ways to provide an impl

anish: MikeE: is there an injection example?

anish: Mark: look in TestSCAClientTestService

anish: s/TestService/GetService/

anish: Mark: line 131

anish: MikeE: that code should be in the vendor code

anish: Mark: yes, that should be updated

anish: MikeE: is the package correct for the impl classes?

anish: ... is org.openoasis.sca enuf or do we need a subpackage?

Vamsi: s/org.openoasis.sca/org.oasisopen.sca  ??

anish: ... client API should be in a separate package

anish: Anish: some of the classes are specific to Java C&I, shouldn't 
they be in a separate package

anish: Mark: the Factory should be common to all Java

anish: Dave: but client factory is something that we expect the vendors 
to implement so that should go in a different package

anish: ... talking about SCAClientFactory

anish: MikeE: i think client classes should be in a separate package

anish: SimonN: we used to have an 'spi' that is gone now

anish: Mark: the SPI got merged into the finder class

anish: ... and that we would provide a ref impl

anish: ... the Finder name was used to follow the same pattern as JAXB

anish: Dave: I'm not getting it, little confused about this

anish: ... don't understand why this isn't an interface

anish: Mark: if vendor chooses to, can use the ref impl. If the vendor 
runs in say OSGi then they can provide their own impl

anish: Dave: yes, but we don't say which methods must be implemented by 
the vendor

anish: ... so we need an interface

anish: SimonN: yes, but the client is still going to call the class and 
not the interface

anish: Mark: but this provides the vendor with the interface that they 
need to implement

anish: SimonN: if we have an interface then we need another factory

anish: Dave: prefer interface over some documentation that the vendor 
has to read. We should prescribe what the vendor implements

anish: Mark: if we want SCAClientFactoryFinder to be an interface then 
we are going away from JAXB pattern

anish vamsi, thx for the correction on the package name

anish: Mark: we could just have the abstract factory and vendors must 
implement it

anish: ... and we would require injection

anish: SimonN: don't like the requirement for management environment, 
won't work for plain SE

anish: Dave: is the vendor throw away our ref impl. Or is that exposed?

anish: s/is/can/

anish: Simon: vendors should not replace the SCAClientFactory

anish: Dave: if vendors can't provide their own class, it doesn't work

anish: ... uncomfortable with vendors shipping code in package that they own

anish: Mark: need to separate classes/interfaces into stuff that client 
sees and stuff that vendors implement

Vamsi: "they own" or "they DON'T own" ?

anish: s/they own/they don't own/

anish thx again vamsi

Vamsi: yw anish

anish: Mark: we need to get a balance between what we specific and what 
the vendor does. Looking for other ideas.

anish: SimonN: why can't you take the finder and inject your own impl?

anish: Dave: yes a vendor can, but we still need an interface

Martin C is waiting to squeak

Vamsi: time up

jeff.mischkinsky: are u going to do straggle roll call?

anish: Dave: need a path for vendor to extend the ClientFactory class 
and the use injection

Martin C squeak piggy squeak

anish: Meeting adjourned


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