Community
Participate
Working Groups
Build ID: M20080911-1700 Steps To Reproduce: Update tuscany.ecore to provide all binding and implementation options (e.g. JScript, Atom) for SCA STP tools. This way users can create composites that take advantages of Tuscany SCA 1.4 features. More information: Meta model defined at http://dev.eclipse.org/svnroot/stp/org.eclipse.stp.sca-tools/org.eclipse.stp.sca/trunk/org.eclipse.stp.sca.domainmodel.tuscany/model/tuscany.ecore
Where can I find the xsd corresponding to the new types defined by Tuscany 1.4? I took a look at the Tuscany svn (modules\assembly-xsd\src\main\resources), but I didn't found the types introduced by Tuscany 1.4 (like google data binding, corba binding, ajax binding, widget implementation, ...).
(In reply to comment #1) > Where can I find the xsd corresponding to the new types defined by Tuscany 1.4? > > I took a look at the Tuscany svn (modules\assembly-xsd\src\main\resources), but > I didn't found the types introduced by Tuscany 1.4 (like google data binding, > corba binding, ajax binding, widget implementation, ...). > True. Unfortunately I think many of these types are validated not via XML parsing, but in the Tuscany model as the inputs are resolved. I will ask on the Tuscany forum and attempt to find an answer. I may be wrong.
Well, it appears after some snooping around and some help from the Tuscany dev list, I am wrong on the XSD information I gave in a previous comment. Tuscany extensions tend to be in the namespace http://tuscany.apache.org/xmlns/sca/1.0 and a schema which pulls these together can be found in: https://svn.apache.org/repos/asf/tuscany/branches/sca-java-1.x/modules/assembly-xsd/src/main/resources/tuscany-sca.xsd
(In reply to comment #3) > Well, it appears after some snooping around and some help from the Tuscany dev > list, I am wrong on the XSD information I gave in a previous comment. > > Tuscany extensions tend to be in the namespace > http://tuscany.apache.org/xmlns/sca/1.0 and a schema which pulls these together > can be found in: > https://svn.apache.org/repos/asf/tuscany/branches/sca-java-1.x/modules/assembly-xsd/src/main/resources/tuscany-sca.xsd > Yes, I know. SCA Tools already takes into account the tuscany namespace and the types defined in the master schema (tuscany-sca.xsd). The problem is that the directory "modules\assembly-xsd\src\main\resources" (and the master schema) doesn't contain the types introduced by Tuscany 1.4 (like google data binding, corba binding, ajax binding, ...). It will be great if you can create the XML schemas of the types that are not defined in the Tuscany svn. It is simplier to generate SCA Tools from the XSD than to make the ecore by hand. I found some information here [http://tuscany.apache.org/sca-java-user-reference.html]. I'm not sure that this information is up-to-date.
Which Tuscany bindings or implementations are missing XSDs? I see the following: > tuscany-binding-corba > tuscany-binding-hessian > tuscany-binding-gdata > tuscany-implementation-jee Any others? I do not see the Ajax binding/impl that you mention. I have asked ont he Tuscany dev list about what people would like to do with these.
I see binding.ajax in the Tuscany user docs, so let's add that to the list too: binding.ajax
I have created Tuscany Jiras 2781-2785 (e.g. http://issues.apache.org/jira/browse/TUSCANY-2781) to track Tuscany creation of the given schemas. Given that these schemas are not part of Tuscany 1.4, I think it is acceptable that the Eclipse STP meta-model for 1.4 be based on the existing schemas in the Tuscany 1.4 branch. No need to wait for these schemas to establish Tuscany 1.4 support.
Tuscany Jiras 2781-2785 are now resolved, and there are now schemas for the following bindings and implementations. > tuscany-binding-corba > tuscany-binding-hessian > tuscany-binding-gdata > tuscany-implementation-jee > tuscany-binding-ajax This is resolved in the Tuscany 1.x branch and will be available at the 1.4.1 or 1.5 release.
Thanks. I'll update the SCA Tools project ASAP.
Fixed. Commit #2883. Tuscany 1.4 is now supported. Dan, if you have an opportunity to test the tools, I'm interested in your feedback. Thanks for your contribution.
Close old bugs.
