[snip]
Florian Rosenberg wrote:
Jean-Sebastien Delfino wrote:
Mike Edwards wrote:
Florian,
I'd point out that the "recommended" way of doing things is to add
things in your own namespace.
Adding stuff to the OSOA XSDs is not encouraged.
If using your own namespace does not work, then we have some work to
do to fix that...
Mike,
+1, the other question is whether or not Florian's extension should be
in the Tuscany namespace.
we plan to contribute our stuff to Tuscany, as soon as we get permission
, so I would rather stick to the Tuscany namespace.
Sounds good :)
My proposed rule of thumb for this:
- if an extension is included in the Tuscany distribution, it can be in
the Tuscany namespace, or a different namespace
- if an extension is not included in the Tuscany distribution, it should
be in a different namespace
Nevertheless, I'll try to use my own namespace and see if it works.
The following should work:
- package your XSD defining its own namespace in your extension, as
described in [1].
- change tuscany-sca.xsd to include your XSD if it belongs to the
Tuscany namespace
I have not tested if what I did in [1] will also allow you to contribute
an XSD belonging to the Tuscany namespace without having to change
tuscany-sca.xsd, but it may work as well :)
[1] http://marc.info/?l=tuscany-user&m=119130076117107
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
