You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Raymond Feng <en...@gmail.com> on 2009/03/05 07:06:36 UTC

Re: [2.x] Progress update on bringing up Tuscany SCA Runtime to the latest OASIS SCA Schemas

This is a good step toward the OASIS SCA. I made more changes under r750323 
to make sure SCA composite and other files in modules/itest/samples/stest 
use the oasis SCA namespace.

Thanks,
Raymond

--------------------------------------------------
From: "Luciano Resende" <lu...@gmail.com>
Sent: Wednesday, March 04, 2009 3:59 PM
To: <de...@tuscany.apache.org>
Subject: [2.x] Progress update on bringing up Tuscany SCA Runtime to the 
latest OASIS SCA Schemas

> We are now using OASIS Namespace and Schemas in our 2.x trunk. While I
> handled changes to all modules and also started providing backward
> compatibility based on our previous discussion [1] to the biggest set
> of processors responsible by dealing with composite processing, there
> are still more things to do (and I'd appreciate help from all the
> community).
>
> - Backward compatibility
>
> The approach I took is to provide a tuscany-module-xml-osoa module
> that would handle the specific osoa schema, contribute processors and
> unit test the specific processors. This is demonstrated in
> assembly-xml-xsd-osoa and assembly-xml-osoa. This would allow maximum
> flexibility for us and any users/embedders as it allows us to produce
> distributions that are OASIS specific (e.g.: by picking up only the
> default OASIS specific modules) or backward capable (e.g by picking up
> OASIS and OSOA set of processors). Note that, while I have done the
> work for our assembly-xsd and assembly-xml, I'd need help from the
> community to get the same pattern applied to the other extensions.
>
> - What's next
>
> Update assembly model based on the latest Assembly spec draft and
> current schemas
> Finish bring-up of modules outside java/modules to use appropriate 
> ns/schema
> Provide extension-xml-osoa modules that would be used for backward 
> compatibility
>
> Please let me know if you have questions/comments...
> And "the pool is open" for everybody to help bringing this up.
>
>
> [1] http://www.mail-archive.com/dev@tuscany.apache.org/msg05656.html
>
> -- 
> Luciano Resende
> Apache Tuscany, Apache PhotArk
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/

Re: [2.x] Progress update on bringing up Tuscany SCA Runtime to the latest OASIS SCA Schemas

Posted by Luciano Resende <lu...@gmail.com>.
On Wed, Mar 11, 2009 at 11:08 PM, Ramkumar R <ra...@gmail.com> wrote:
> Hi Luciano,
>
> Thanks for listing them down, I would like to help in the following item....
>
> - Identify changes from new Schema and update respective processors
> (we could possibly divide here in core, bindings, implementations)
>
> like to start with implementations first, and then move to bindings and
> core.
>

That's awesome !!! Maybe just send an e-mail when you complete each
one of this (implementation, bindings)... so we can make sure people
won't duplicate work.


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

Re: [2.x] Progress update on bringing up Tuscany SCA Runtime to the latest OASIS SCA Schemas

Posted by Ramkumar R <ra...@gmail.com>.
Hi Luciano,

Thanks for listing them down, I would like to help in the following item....

- Identify changes from new Schema and update respective processors
(we could possibly divide here in core, bindings, implementations)

like to start with implementations first, and then move to bindings and
core.

On Mon, Mar 9, 2009 at 11:18 PM, Luciano Resende <lu...@gmail.com>wrote:

> For folks trying to help, couple items could be next :
>
> - Update the Assembly model based on the new OSOA schemas
> - Identify changes from new Schema and update respective processors
> (we could possibly divide here in core, bindings, implementations)
> - Work on items from the "OASIS versus OSOA delta" items [1] and
> choose the ones related to schema/models
>
> I'll try to get this thread updated with other items as they come to
> mind, others please feel free to grab some items or suggest new ones.
>
> [1]
> http://cwiki.apache.org/confluence/display/TUSCANYWIKI/OSOA+SCA+vs+OASIS+SCA
>
> On Thu, Mar 5, 2009 at 9:43 PM, Luciano Resende <lu...@gmail.com>
> wrote:
> > I have completed necessary updates to use the new OASIS namespace and
> > schemas released today.
> >
> > I have found some issues with the schemas released today, and
> > workarounded/fixed them in our code. I have also reported these issues
> > back to OASIS Spec Group.
> >
> > On Thu, Mar 5, 2009 at 2:36 PM, Luciano Resende <lu...@gmail.com>
> wrote:
> >> Well, I guess the OASIS Open CSA just changed the NS to be used [1],
> >> and provided a new set of XSDs.
> >> I'll start reviewing what needs to be changed in our side... again...
> >>
> >> [1]
> http://www.oasis-open.org/apps/org/workgroup/sca-assembly/email/archives/200903/msg00077.html
> >>
> >> On Thu, Mar 5, 2009 at 10:23 AM, Raymond Feng <en...@gmail.com>
> wrote:
> >>> Do you expect us to support 3 versions of the SCA specs in Tuscany :-)
> ?
> >>>
> >>> I think the <xyz>-xml module should be the aligned with the level of
> model
> >>> in <xyz> module. For example, we have OASIS SCA 1.1 based model in
> >>> "assembly", then I imagine that "assembly-xml" has the processors for
> SCA
> >>> 1.1. "<xyz>-xml-<osoa>" will be the compatibility layer (Some Eclipse
> >>> plugins use the "compatibility" as part of the ids for similar cases).
> >>>
> >>> Would the following be a better naming?
> >>>
> >>> assembly-xml-compatibility-sca10
> >>>
> >>> Thanks,
> >>> Raymond
> >>>
> >>> From: Simon Laws
> >>> Sent: Thursday, March 05, 2009 8:45 AM
> >>> To: dev@tuscany.apache.org
> >>> Subject: Re: [2.x] Progress update on bringing up Tuscany SCA Runtime
> to the
> >>> latest OASIS SCA Schemas
> >>>
> >>>
> >>> Hi Raymond
> >>>
> >>> snip...
> >>>
> >>>
> >>>
> >>> For OASIS: org.apache.tuscany.sca.assembly.xml
> >>> For OSOA: org.apache.tuscany.sca.assembly.xml.osoa
> >>>
> >>>
> >>>
> >>> So what happens when OASIS release a new spec version after v1.1? I
> don't
> >>> know that they will of course but just thinking ahead.
> >>>
> >>> Simon
> >>>
> >>
> >>
> >>
> >> --
> >> Luciano Resende
> >> Apache Tuscany, Apache PhotArk
> >> http://people.apache.org/~lresende<http://people.apache.org/%7Elresende>
> >> http://lresende.blogspot.com/
> >>
> >
> >
> >
> > --
> > Luciano Resende
> > Apache Tuscany, Apache PhotArk
> > http://people.apache.org/~lresende<http://people.apache.org/%7Elresende>
> > http://lresende.blogspot.com/
> >
>
>
>
> --
> Luciano Resende
> Apache Tuscany, Apache PhotArk
> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
> http://lresende.blogspot.com/
>



-- 
Thanks & Regards,
Ramkumar Ramalingam

Re: [2.x] Progress update on bringing up Tuscany SCA Runtime to the latest OASIS SCA Schemas

Posted by Luciano Resende <lu...@gmail.com>.
For folks trying to help, couple items could be next :

- Update the Assembly model based on the new OSOA schemas
- Identify changes from new Schema and update respective processors
(we could possibly divide here in core, bindings, implementations)
- Work on items from the "OASIS versus OSOA delta" items [1] and
choose the ones related to schema/models

I'll try to get this thread updated with other items as they come to
mind, others please feel free to grab some items or suggest new ones.

[1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/OSOA+SCA+vs+OASIS+SCA

On Thu, Mar 5, 2009 at 9:43 PM, Luciano Resende <lu...@gmail.com> wrote:
> I have completed necessary updates to use the new OASIS namespace and
> schemas released today.
>
> I have found some issues with the schemas released today, and
> workarounded/fixed them in our code. I have also reported these issues
> back to OASIS Spec Group.
>
> On Thu, Mar 5, 2009 at 2:36 PM, Luciano Resende <lu...@gmail.com> wrote:
>> Well, I guess the OASIS Open CSA just changed the NS to be used [1],
>> and provided a new set of XSDs.
>> I'll start reviewing what needs to be changed in our side... again...
>>
>> [1] http://www.oasis-open.org/apps/org/workgroup/sca-assembly/email/archives/200903/msg00077.html
>>
>> On Thu, Mar 5, 2009 at 10:23 AM, Raymond Feng <en...@gmail.com> wrote:
>>> Do you expect us to support 3 versions of the SCA specs in Tuscany :-) ?
>>>
>>> I think the <xyz>-xml module should be the aligned with the level of model
>>> in <xyz> module. For example, we have OASIS SCA 1.1 based model in
>>> "assembly", then I imagine that "assembly-xml" has the processors for SCA
>>> 1.1. "<xyz>-xml-<osoa>" will be the compatibility layer (Some Eclipse
>>> plugins use the "compatibility" as part of the ids for similar cases).
>>>
>>> Would the following be a better naming?
>>>
>>> assembly-xml-compatibility-sca10
>>>
>>> Thanks,
>>> Raymond
>>>
>>> From: Simon Laws
>>> Sent: Thursday, March 05, 2009 8:45 AM
>>> To: dev@tuscany.apache.org
>>> Subject: Re: [2.x] Progress update on bringing up Tuscany SCA Runtime to the
>>> latest OASIS SCA Schemas
>>>
>>>
>>> Hi Raymond
>>>
>>> snip...
>>>
>>>
>>>
>>> For OASIS: org.apache.tuscany.sca.assembly.xml
>>> For OSOA: org.apache.tuscany.sca.assembly.xml.osoa
>>>
>>>
>>>
>>> So what happens when OASIS release a new spec version after v1.1? I don't
>>> know that they will of course but just thinking ahead.
>>>
>>> Simon
>>>
>>
>>
>>
>> --
>> Luciano Resende
>> Apache Tuscany, Apache PhotArk
>> http://people.apache.org/~lresende
>> http://lresende.blogspot.com/
>>
>
>
>
> --
> Luciano Resende
> Apache Tuscany, Apache PhotArk
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
>



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

Re: [2.x] Progress update on bringing up Tuscany SCA Runtime to the latest OASIS SCA Schemas

Posted by Luciano Resende <lu...@gmail.com>.
I have completed necessary updates to use the new OASIS namespace and
schemas released today.

I have found some issues with the schemas released today, and
workarounded/fixed them in our code. I have also reported these issues
back to OASIS Spec Group.

On Thu, Mar 5, 2009 at 2:36 PM, Luciano Resende <lu...@gmail.com> wrote:
> Well, I guess the OASIS Open CSA just changed the NS to be used [1],
> and provided a new set of XSDs.
> I'll start reviewing what needs to be changed in our side... again...
>
> [1] http://www.oasis-open.org/apps/org/workgroup/sca-assembly/email/archives/200903/msg00077.html
>
> On Thu, Mar 5, 2009 at 10:23 AM, Raymond Feng <en...@gmail.com> wrote:
>> Do you expect us to support 3 versions of the SCA specs in Tuscany :-) ?
>>
>> I think the <xyz>-xml module should be the aligned with the level of model
>> in <xyz> module. For example, we have OASIS SCA 1.1 based model in
>> "assembly", then I imagine that "assembly-xml" has the processors for SCA
>> 1.1. "<xyz>-xml-<osoa>" will be the compatibility layer (Some Eclipse
>> plugins use the "compatibility" as part of the ids for similar cases).
>>
>> Would the following be a better naming?
>>
>> assembly-xml-compatibility-sca10
>>
>> Thanks,
>> Raymond
>>
>> From: Simon Laws
>> Sent: Thursday, March 05, 2009 8:45 AM
>> To: dev@tuscany.apache.org
>> Subject: Re: [2.x] Progress update on bringing up Tuscany SCA Runtime to the
>> latest OASIS SCA Schemas
>>
>>
>> Hi Raymond
>>
>> snip...
>>
>>
>>
>> For OASIS: org.apache.tuscany.sca.assembly.xml
>> For OSOA: org.apache.tuscany.sca.assembly.xml.osoa
>>
>>
>>
>> So what happens when OASIS release a new spec version after v1.1? I don't
>> know that they will of course but just thinking ahead.
>>
>> Simon
>>
>
>
>
> --
> Luciano Resende
> Apache Tuscany, Apache PhotArk
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
>



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

Re: [2.x] Progress update on bringing up Tuscany SCA Runtime to the latest OASIS SCA Schemas

Posted by Luciano Resende <lu...@gmail.com>.
Well, I guess the OASIS Open CSA just changed the NS to be used [1],
and provided a new set of XSDs.
I'll start reviewing what needs to be changed in our side... again...

[1] http://www.oasis-open.org/apps/org/workgroup/sca-assembly/email/archives/200903/msg00077.html

On Thu, Mar 5, 2009 at 10:23 AM, Raymond Feng <en...@gmail.com> wrote:
> Do you expect us to support 3 versions of the SCA specs in Tuscany :-) ?
>
> I think the <xyz>-xml module should be the aligned with the level of model
> in <xyz> module. For example, we have OASIS SCA 1.1 based model in
> "assembly", then I imagine that "assembly-xml" has the processors for SCA
> 1.1. "<xyz>-xml-<osoa>" will be the compatibility layer (Some Eclipse
> plugins use the "compatibility" as part of the ids for similar cases).
>
> Would the following be a better naming?
>
> assembly-xml-compatibility-sca10
>
> Thanks,
> Raymond
>
> From: Simon Laws
> Sent: Thursday, March 05, 2009 8:45 AM
> To: dev@tuscany.apache.org
> Subject: Re: [2.x] Progress update on bringing up Tuscany SCA Runtime to the
> latest OASIS SCA Schemas
>
>
> Hi Raymond
>
> snip...
>
>
>
> For OASIS: org.apache.tuscany.sca.assembly.xml
> For OSOA: org.apache.tuscany.sca.assembly.xml.osoa
>
>
>
> So what happens when OASIS release a new spec version after v1.1? I don't
> know that they will of course but just thinking ahead.
>
> Simon
>



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

Re: [2.x] Progress update on bringing up Tuscany SCA Runtime to the latest OASIS SCA Schemas

Posted by Raymond Feng <en...@gmail.com>.
Do you expect us to support 3 versions of the SCA specs in Tuscany :-) ?

I think the <xyz>-xml module should be the aligned with the level of model 
in <xyz> module. For example, we have OASIS SCA 1.1 based model in 
"assembly", then I imagine that "assembly-xml" has the processors for SCA 
1.1. "<xyz>-xml-<osoa>" will be the compatibility layer (Some Eclipse 
plugins use the "compatibility" as part of the ids for similar cases).

Would the following be a better naming?

assembly-xml-compatibility-sca10

Thanks,
Raymond

From: Simon Laws
Sent: Thursday, March 05, 2009 8:45 AM
To: dev@tuscany.apache.org
Subject: Re: [2.x] Progress update on bringing up Tuscany SCA Runtime to the 
latest OASIS SCA Schemas


Hi Raymond

snip...



For OASIS: org.apache.tuscany.sca.assembly.xml
For OSOA: org.apache.tuscany.sca.assembly.xml.osoa



So what happens when OASIS release a new spec version after v1.1? I don't 
know that they will of course but just thinking ahead.

Simon

Re: [2.x] Progress update on bringing up Tuscany SCA Runtime to the latest OASIS SCA Schemas

Posted by Simon Laws <si...@googlemail.com>.
Hi Raymond

snip...

>
> For OASIS: org.apache.tuscany.sca.assembly.xml
> For OSOA: org.apache.tuscany.sca.assembly.xml.osoa
>
>
So what happens when OASIS release a new spec version after v1.1? I don't
know that they will of course but just thinking ahead.

Simon

Re: [2.x] Progress update on bringing up Tuscany SCA Runtime to the latest OASIS SCA Schemas

Posted by Raymond Feng <en...@gmail.com>.
Yes, we'll have to change the package names to avoid split packages in OSGi. To follow the same naming convention, I propose a slight different scheme:

For OASIS: org.apache.tuscany.sca.assembly.xml
For OSOA: org.apache.tuscany.sca.assembly.xml.osoa


Thanks,
Raymond


From: Simon Laws 
Sent: Thursday, March 05, 2009 7:26 AM
To: dev@tuscany.apache.org 
Subject: Re: [2.x] Progress update on bringing up Tuscany SCA Runtime to the latest OASIS SCA Schemas





On Thu, Mar 5, 2009 at 6:06 AM, Raymond Feng <en...@gmail.com> wrote:

  This is a good step toward the OASIS SCA. I made more changes under r750323 to make sure SCA composite and other files in modules/itest/samples/stest use the oasis SCA namespace.

  Thanks,
  Raymond

  --------------------------------------------------
  From: "Luciano Resende" <lu...@gmail.com>
  Sent: Wednesday, March 04, 2009 3:59 PM
  To: <de...@tuscany.apache.org>
  Subject: [2.x] Progress update on bringing up Tuscany SCA Runtime to the latest OASIS SCA Schemas 
  - Show quoted text -



    We are now using OASIS Namespace and Schemas in our 2.x trunk. While I
    handled changes to all modules and also started providing backward
    compatibility based on our previous discussion [1] to the biggest set
    of processors responsible by dealing with composite processing, there
    are still more things to do (and I'd appreciate help from all the
    community).

    - Backward compatibility

    The approach I took is to provide a tuscany-module-xml-osoa module
    that would handle the specific osoa schema, contribute processors and
    unit test the specific processors. This is demonstrated in
    assembly-xml-xsd-osoa and assembly-xml-osoa. This would allow maximum
    flexibility for us and any users/embedders as it allows us to produce
    distributions that are OASIS specific (e.g.: by picking up only the
    default OASIS specific modules) or backward capable (e.g by picking up
    OASIS and OSOA set of processors). Note that, while I have done the
    work for our assembly-xsd and assembly-xml, I'd need help from the
    community to get the same pattern applied to the other extensions.

    - What's next

    Update assembly model based on the latest Assembly spec draft and
    current schemas
    Finish bring-up of modules outside java/modules to use appropriate ns/schema
    Provide extension-xml-osoa modules that would be used for backward compatibility

    Please let me know if you have questions/comments...
    And "the pool is open" for everybody to help bringing this up.


    [1] http://www.mail-archive.com/dev@tuscany.apache.org/msg05656.html

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




Thanks Luciano for pushing this along. 

Re. backward compatibility. How about we also change the package names in the xml modules so that there are no clashes? Something like

org.apache.tuscany.sca.assembly.xml
org.apache.tuscany.sca.assembly.v11.xml

I'm in the builders at the moment looking at Endpoints. There are different semantics here in OASIS compared to OSOA. I'll think about how we represent this variability. My first thought is that we add the sca namespace to the composite model that has been read and use this infromation as appropriate. Builders now have an extension point so we have the option of extending this to load versioned builders or even doing version specific processing inside the builders. I think the first is the most obvious approach.

Simon

Re: [2.x] Progress update on bringing up Tuscany SCA Runtime to the latest OASIS SCA Schemas

Posted by Simon Laws <si...@googlemail.com>.
On Thu, Mar 5, 2009 at 6:06 AM, Raymond Feng <en...@gmail.com> wrote:

> This is a good step toward the OASIS SCA. I made more changes under r750323
> to make sure SCA composite and other files in modules/itest/samples/stest
> use the oasis SCA namespace.
>
> Thanks,
> Raymond
>
> --------------------------------------------------
> From: "Luciano Resende" <lu...@gmail.com>
> Sent: Wednesday, March 04, 2009 3:59 PM
> To: <de...@tuscany.apache.org>
> Subject: [2.x] Progress update on bringing up Tuscany SCA Runtime to the
> latest OASIS SCA Schemas- Show quoted text -
>
>
>  We are now using OASIS Namespace and Schemas in our 2.x trunk. While I
>> handled changes to all modules and also started providing backward
>> compatibility based on our previous discussion [1] to the biggest set
>> of processors responsible by dealing with composite processing, there
>> are still more things to do (and I'd appreciate help from all the
>> community).
>>
>> - Backward compatibility
>>
>> The approach I took is to provide a tuscany-module-xml-osoa module
>> that would handle the specific osoa schema, contribute processors and
>> unit test the specific processors. This is demonstrated in
>> assembly-xml-xsd-osoa and assembly-xml-osoa. This would allow maximum
>> flexibility for us and any users/embedders as it allows us to produce
>> distributions that are OASIS specific (e.g.: by picking up only the
>> default OASIS specific modules) or backward capable (e.g by picking up
>> OASIS and OSOA set of processors). Note that, while I have done the
>> work for our assembly-xsd and assembly-xml, I'd need help from the
>> community to get the same pattern applied to the other extensions.
>>
>> - What's next
>>
>> Update assembly model based on the latest Assembly spec draft and
>> current schemas
>> Finish bring-up of modules outside java/modules to use appropriate
>> ns/schema
>> Provide extension-xml-osoa modules that would be used for backward
>> compatibility
>>
>> Please let me know if you have questions/comments...
>> And "the pool is open" for everybody to help bringing this up.
>>
>>
>> [1] http://www.mail-archive.com/dev@tuscany.apache.org/msg05656.html
>>
>> --
>> Luciano Resende
>> Apache Tuscany, Apache PhotArk
>> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
>> http://lresende.blogspot.com/
>>
>
>
Thanks Luciano for pushing this along.

Re. backward compatibility. How about we also change the package names in
the xml modules so that there are no clashes? Something like

org.apache.tuscany.sca.assembly.xml
org.apache.tuscany.sca.assembly.v11.xml

I'm in the builders at the moment looking at Endpoints. There are different
semantics here in OASIS compared to OSOA. I'll think about how we represent
this variability. My first thought is that we add the sca namespace to the
composite model that has been read and use this infromation as appropriate.
Builders now have an extension point so we have the option of extending this
to load versioned builders or even doing version specific processing inside
the builders. I think the first is the most obvious approach.

Simon