Jean-Sebastien Delfino wrote:
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...
Hi all,
I spent a lot of time in Eclipse developing Tuscany samples and demos
recently. I found myself tweaking my various Eclipse workspaces again
and again to do the following:
- Define a Tuscany User Library containing all the Tuscany JARs to make
it easier to add them to my project buildpath.
- Associate .composite files with the XML editor and register the SCA
and Tuscany XML schemas to get code-assist in the editor and validation
of my composite files.
- Write programs to launch Tuscany configured with my various
composites... wishing that I could just right-click on the .composite
and select a Run As / Tuscany...
I'm sure I'm not alone doing these tweaks, again and again... so I
committed under java/sca/tools a strawman implementation of two small
Eclipse plugins that configure Tuscany in Eclipse automatically :) They
should make Tuscany much easier to use in Eclipse.
Module tools/plugin-runtime packages the Tuscany runtime Jars in a
Tuscany User Library which can be added to a project buildpath.
Module tools/plugin-core:
- Associates .composite files with the Eclipse WTP XML editor
- Registers the SCA and Tuscany XMLSchemas with it, providing XMLSchema
based content assist and validation when you edit .composite files.
- Declares a launcher that allows you to do Run As / Tuscany on a
.composite file.
I also put the beginning of an Eclipse feature and updatesite under
tools/feature and tools/updatesite.
This is all pretty rough. In particular I'm not sure how to build
plugin-core, the feature and updatesite with Maven as the Maven module
structure does not seem to fit well with what the Eclipse plugin
development environment expects.
One of the next steps - if people are interested - could be to add more
complete validation of .composite files, for example check that
reference targets or component implementation classes exist, basically
cover what cannot be validated with just XML schema.
Another thing that has been bothering me when building Webapps with
Tuscany recently is the 5 lines I needed to add to each web.xml file to
register the Tuscany servlet filter. A tool could add these lines
automatically for example.
Thoughts? Is anybody interested in helping with this?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
