Jean-Sebastien Delfino wrote: >I spent a lot of time in Eclipse developing Tuscany samples and demos recently. I agree this is definitely a pita.
>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... You are not :-) >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. That is awesome. >Module tools/plugin-runtime packages the Tuscany runtime Jars in a >Tuscany User Library which can be added to a project buildpath. Simple and neat. >Module tools/plugin-core: >- Associates .composite files with the Eclipse WTP XML editor NB: You did not add any depdencies to the feature, making it hard to use. See patch pointer below. >- 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. What else dowe need. Nice! >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. I already did help setup a maven/eclipse builds for Drools (Apache licensed). I could give a hand there. >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. That could be done with some Eclipse webtools extension >Thoughts? Is anybody interested in helping with this? Being an Eclipse wonk, I could be interested... but keep your expections low. In the meantime I created a jira and attached a small patch that fixes some minor configurations issues: - make it so that Eclipse appends a date time stamp to a built plugin (.qualifier) and let features update its contained plugins versions on build. - added missing features dependencies - fixed the build.properties and manifest for minor inconsistencies and missing execution envt constraints, which I did set to Java 5 as a minimum. See https://issues.apache.org/jira/browse/TUSCANY-1805 PS: You guys probably are wondering who I am. I have been lurking around watching tuscany for a while, waiting in the shadows for something to happen tools wise. I getting out of the closet now that something is hapening on that front! I am an open source enthusisast, and committer at Eclipse and JBoss, as well as maintainer of EasyEclipse an open source distro of plugins. See http://google.com/search?q=%22philippe%20ombredanne%22 Cordially -- Cheers Philippe http://easyeclipse.org - http://phpeclipse.net - http://eclipse.org/atf --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
