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: Sharing Java artifacts across contributions


This is now Issue 60. See:

 

http://www.osoa.org/jira/browse/JAVA-60

 

Thanks,

 

Mark

Mark Combellack| Software Developer| Avaya | Eastern Business Park | St. Mellons | Cardiff | CF3 5EA | Voice: +44 (0) 29 2081 7624 | mcombellack@avaya.com


From: David Booz [mailto:booz@us.ibm.com]
Sent: 29 August 2008 16:50
To: sca-j@lists.oasis-open.org
Subject: [sca-j] NEW ISSUE: Sharing Java artifacts across contributions

 

TARGET: Java C&I spec

DESCRIPTION:
The SCA Assembly spec defines a means for sharing XML artifacts across SCA contributions. While some aspects of this are actively being debated (http://www.osoa.org/jira/browse/ASSEMBLY-8) as an issue, the same consideration of shared artifacts needs to be addressed by the Java TC. Chiefly the question is how to enable sharing of Java artifacts (Interfaces, JAXB objects, SDOs, potentially even component implementation classes, etc) across contributions such that a referring contribution can make use of Java artifacts from a referred to contribution.

PROPOSAL: None, but my mental model starts with something called import.java/export.java, as an extension of the base assembly import/export model.


Dave Booz
STSM, BPM and SCA Architecture
Co-Chair OASIS SCA-Policy TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093
e-mail:booz@us.ibm.com



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