Jeremy Boynes wrote:
On Jan 24, 2007, at 1:22 PM, Jean-Sebastien Delfino wrote:
The C++ runtime allows bindings and component implementation types to
share a common Tuscany namespace and updates to them do not require
an update of the Kernel. We simply load the SCDL XSD files out of
each runtime extension directory and they can contribute to a common
namespace.
As far as I know the Java runtime does not load or make any use of
the SCDL XSDs at this point, so I don't understand what the issues
would be with the Java runtime.
The bindings and component implementation types defined by the OSOA
specs are in a single OSOA namespace. I think that the bindings and
component implementation types introduced by the Tuscany project
should be in a single Tuscany namespace.
Extensions provided by other projects can be in other namespaces
obviously.
How does this scheme address the versioning issues associated with XML
namespaces?
Could you explain what you mean by this?
The spec addresses them by coordinating releases from all binding and
implementation groups.
Is that right? I am not aware that all specs sharing the OSOA namespace
are going to be released at the same time. I understand that the SCA
core namespace needs to be released before the extensions, but I can
imagine different extensions being released independently. If there are
dependencies between the various XSDs (for example a complex type
extending another one) their updates obviously need to coordinated but
this would be true with multiple namespaces as well.
Doing the same in Tuscany would take us back to a model where we need
to coordinate kernel and all extension releases which is something we
have decided not to do (for very good reasons).
Like I said before I don't think that we need to update the kernel when
extensions change. The Tuscany C++ runtime for example picks up
extension XSDs from extension directories independent of the kernel, and
is able to pick up newer versions of these XSDs without any change in
the kernel. The Java runtime could do the same, but again at the moment
it does not load or make any use of the XSDs anyway...
I still don't see any concrete issue at this point.
--
Jeremy
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
