Re: [stp-dev] Tuscany and STP-SCA tools

[Luciano Resende <lresende@xxxxxxxxxx>]

Hi Stephane

   The missing Tuscany XSD schemas are now available in [1].
   Do you need them in the "release" or are you going to use them to
generate ecore file only ?

[1] https://svn.apache.org/repos/asf/tuscany/branches/sca-java-1.x/modules/assembly-xsd/src/main/resources/


On Fri, Jan 16, 2009 at 2:05 AM, Stéphane Drapeau
<Stephane.Drapeau@xxxxxxx> wrote:
> Luciano Resende a écrit :
>>
>> On Thu, Jan 15, 2009 at 9:18 AM, Dan Becker <dan.o.becker@xxxxxxxxx>
>> wrote:
>>
>>>
>>> Stéphane Drapeau wrote:
>>>
>>>>
>>>> That would be great if you can submit a bug describing the elements you
>>>> want
>>>> to add or modify. But before this, I'll try to generate the ecore file
>>>> from
>>>> the Tuscany XDS schema. I hope that I will find some time to do this
>>>> before
>>>> the end of this week. I'll keep you informed ASAP.
>>>>
>>>> I have several questions:
>>>> - Do you want that we update the tools according to Tuscany 1.4 or to
>>>> Tuscany 2.0? Is there any differences beetween these two versions (from
>>>> type
>>>> definition viewpoint)?
>>>> - For the next SCA Tools releases, does it make sense for you to have a
>>>> specific MM for each version of Tuscany? Or one for the 1.x branch and
>>>> an
>>>> other for the 2.x branch? or only one corresponding to the last stable
>>>> version of Tuscany?
>>>>
>>>>
>>>
>>> Excellent! I've opened bug 261222 [1] to track the issue.
>>>
>
> Thanks Dan. I have a question for you. Have a look at the bug.
>>>
>>> Tuscany 2.0 will go through a few milestone releases before going golden,
>>> so
>>> I think 2.0 will be available much later in the year. As the primary
>>> feature
>>> of 2.0 will be OSGi enablement, the binding and implementation list will
>>> not
>>> be much different than the current 1.4.
>>>
>>> I think it will be sufficient to make models for each point release e.g.
>>> 1.4, 2.0, 2.1 etc.. There should be no new features in the maintenance
>>> releases (e.g. 1.4.0, 1.4.1, etc.)
>>>
>>>
>>
>> How does STP-SCA tools differentiate multiple Tuscany 1.x releases ?
>>
>
> My idea is to have specific plugins for each Tuscany release. Plugins for a
> specific Tucany release will extend the SCA Composite Designer (to add the
> types provided by this Tuscany release).
> For this purpose, each meta model must use a different namespace :
> - http://tuscany.apache.org/xmlns/sca/1.4
> - http://tuscany.apache.org/xmlns/sca/2.0
>
>> What happens if a user is using Tuscany Java SCA 1.2 release compared
>> to Tuscany Java SCA 1.4 that has introduced couple new bindings (e.g
>> google data, corba, etc) ?
>
> If the user install SCA Tools for Tuscany 1.2 (Tuscany 1.4), he can only
> edit types defined by Tuscany 1.2 (Tuscany 1.4).
>>
>> Do we always make all the latest bindings
>> available for users ?
>>
>
> No.
>>
>>
>>>
>>> [1]https://bugs.eclipse.org/bugs/show_bug.cgi?id=261222
>>>
>>> --
>>> Thanks, Dan Becker
>>> _______________________________________________
>>> stp-dev mailing list
>>> stp-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/stp-dev
>>>
>>>
>>
>>
>>
>>
>
>



-- 
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/