Jeremy Boynes wrote:
-1 on the single namespace as it couples together all the extensions -
we would need to create a new version of the namespace every time any
extension changed its XML
--
Jeremy
On Jan 23, 2007, at 4:35 AM, ant elder (JIRA) wrote:
[
https://issues.apache.org/jira/browse/TUSCANY-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder reassigned TUSCANY-1053:
----------------------------------
Assignee: ant elder
Use a Tuscany namespace for all non-spec'd Tuscany extensions
-------------------------------------------------------------
Key: TUSCANY-1053
URL: https://issues.apache.org/jira/browse/TUSCANY-1053
Project: Tuscany
Issue Type: Improvement
Affects Versions: Java-M2
Reporter: ant elder
Assigned To: ant elder
Fix For: Java-SCA-M3
Currently Tsucany extensions use SCDL elements is varrious different
namespaces. There should be a single Tuscany namespace that
extensions not defined by SCA spec's should use. See
http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200701.mbox/[EMAIL PROTECTED]
--This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
I prefer a single Tuscany namespace. This is what the OSOA specs are
doing as well with a single SCA namespace for everything. This helps
simplfy the programming model as application developers only need to
declare the single namespace at the top of an SCDL file instead of
having to list different namespaces for all the bindings, implementation
types, policies etc. that they use.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
