Next in thread →
Next in month →
RE: [sca-j] ISSUE 60 - Sharing Java artifacts across contributions -proposal
Mark, Thanks for the comments. Responses inline as <mje>..</mje> 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: From: "Mark Combellack" <> To: <> Cc: "David Booz" <> Date: 19/01/2009 10:17 Subject: RE: [sca-j] ISSUE 60 - Sharing Java artifacts across contributions - proposal Hi, A few comments regarding this proposal: General: Assumption: I am assuming that the import.java and export.java are based on the Import-Package and Export-Package OSGI concepts Is it worth mentioning that we do not support wildcard imports (i.e. the use of “*” in the package name) like the DynamicImport-Package OSGI concept <mje> Correct - this proposal is equivalent to import-package and export-package of OSGi. </mje> General: Can I have multiple import and export statements in my sca-contribution.xml? Or do I have to comma separate them all on a single import/export statement? <mje> Yes, multiple are allowed - this is expressed in the contribution.xsd contained in the SCA Assembly spec </mje> Is this allowed? <contribution ...> ... <import.java package=”myfirstpackage”/> <import.java package=”mysecondpackage”/> <export.java package=”some.xml.parser”/> <import.java package=”some.soap.stack”/> ... </contribution> <mje>Yes, allowed</mje> I am presuming that the XML schema would give me the answer but it is unclear from the text if this is allowed. <mje> I've tried to clarify the wording </mje> Line 571: Text has “The name of one or more Java package” This should be changed to “package(s)” to match the text on line 544 <mje>Done</mje> Lines 583 -> 592: I would consider extending the example to import more than 1 package and use at least one version number somewhere. For example, replace the text on lines 583 to 592 with: For example, a contribution that wants to: · Use classes from the some.package package · Use version 2.0 of the classes from the some.other.package package · expose the my.package package from its own contribution, would specify an sca-contribution.xml file as follows: <?xml version="1.0" encoding="ASCII"?> <contribution xmlns=http://docs.oasis-open.org/ns/opencsa/sca/200712> … <import.java package=”some.package,some.other.package;version=2.0”/> <export.java package=”my.package”/> </contribution> <mje> Done - nice enhancement to the example, thanks</mje> Note: If more than one import.java statement is allowed, it might be clearer to separate the import statements into two in the above example. <mje> Done</mje> Thanks, Mark Mark Combellack| Software Developer| Avaya | Eastern Business Park | St. Mellons | Cardiff | CF3 5EA | Voice: +44 (0) 29 2081 7624 | > -----Original Message----- > From: C Vamsi [mailto:] > Sent: 18 January 2009 08:18 > To: David Booz > Cc: > Subject: Re: [sca-j] ISSUE 60 - Sharing Java artifacts across > contributions - proposal > > Some comments from a first scan of the attached doc: > > 1. At line 570, I guess it should be export.java instead of import.java. > > ++Vamsi > Apache Tuscany Committer http://tuscany.apache.org > Apache Geronimo Committer and Member of PMC http://geronimo.apache.org > > > > > David Booz > <> > To > 17/01/2009 19:06 > cc > > Subject > [sca-j] ISSUE 60 - Sharing Java > artifacts across contributions - > proposal > > > > > > > > > > > > Attached is my proposal for a resolution to issue 60. The changes are > almost entirely in a new chapter 11 "Java Packaging and Deployment Model". > This was a collaboration with Mike E, so some of the updates are his. > > (See attached file: sca-javaci-1.1-spec-wd02_issue60.doc) > > Dave Booz > STSM, BPM and SCA Architecture > Co-Chair OASIS SCA-Policy TC and SCA-J TC > "Distributed objects first, then world hunger" > Poughkeepsie, NY (845)-435-6093 or 8-295-6093 > e-mail:[attachment "sca-javaci-1.1-spec-wd02_issue60.doc" > deleted by C Vamsi/India/IBM] > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 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
Next in thread →
Next in month →