I'm not very happy with the decision
that Mary sent out. The package prefix she is suggesting seems very
cumbersome and contrary to normal Java naming conventions. We'll
all have to get used to saying "org dot oasis underscore open dot
sca dot ComponentContext" (etc.).
It's the cumbersome and unconventional
new package name prefix that is the main issue from my perspective. The
change from osoa could be argued either way, depending on how much change
we make to the details of the APIs.
Simon
Simon C. Nash, IBM Distinguished Engineer
Member of the IBM Academy of Technology
Tel. +44-1962-815156 Fax +44-1962-818999
"Barack, Ron"
<>
28/02/2008 13:41
To
"Patil, Sanjay" <>,
<>
cc
Subject
[sca-j] ISSUE-28: Package Name Changes
http://www.osoa.org/jira/browse/JAVA-28
Von: Patil, Sanjay [mailto:]
Gesendet: Donnerstag, 21. Februar 2008 19:50
An:
Betreff: [sca-j] NEW ISSUE: Package Name Changes
RAISER: Sanjay Patil
TARGET: Java Common Annotations and APIs Specification
DESCRIPTION:
The Java Common Annotations and APIs Specification uses the 'org.osoa.sca'
package name for the API and 'org.osoa.sca.annotations' package name for
the annotations. There
exist a good number of commercial and open source software implementations
of SCA that use the current package names. It will be painful for these
implementations to maintain backward compatibility if the package names
in the final version of the specifications are going to be different
from the current package names.
It is not clear whether the OASIS SCA-J TC
would bless use of the current package names in the final versions of the
specifications or not.
PROPOSAL:
Continue to use the current package names (org.osoa.sca, org.osoa.sca.annotations)
in the final specifications.
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
