ant elder wrote:
On 9/7/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
This has come up several times but I've not seen any conclusion.
Here are the relevant JIRAs:
http://issues.apache.org/jira/browse/TUSCANY-181
http://issues.apache.org/jira/browse/TUSCANY-678
http://issues.apache.org/jira/browse/TUSCANY-1389
To resolve these JIRAs I think we should include the SCA XSDs [1] in the
Tuscany distribution.
Is there any issue with the SCA license [2] preventing us to include the
XSDs?
Is the license going to change now that SCA is being standardized at
OASIS?
Thoughts?
[1] http://www.osoa.org/xmlns/sca/1.0/
[2] http://www.osoa.org/xmlns/sca/1.0/license.txt
--
Jean-Sebastien
I think it should be fine to include them as we already include some other
things which also use that OSOA license in previous SCA and SDO releases.
It would be interesting to know if the license will be changed to something
more standard with the move to OASIS.
...ant
OK, if there's no objection, I'll go ahead and include the XSDs. This
will allow us to do a number of interesting things:
- Validate SCA assembly XML when loading .composite, .componentType,
.constrainingType, improving our error reporting story. I'll try to see
how we can just leverage Validating StAX XMLStreamReaders for that.
- Document how to register the XSDs in an IDE like Eclipse and get
validation there too, again improving the error reporting story. We may
even be able to provide a simple plugin.xml file that you can drop in
your IDE and does the XSD registration for you.
- Define XSDs for our various implementation and binding extensions,
extending the core SCA XSDs. I think it is important to help document them.
More on this in the next 2 days if I find a little bit of time to work
on it...
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
