You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@tuscany.apache.org by Jean-Sebastien Delfino <js...@apache.org> on 2007/08/06 23:06:25 UTC

Contents of Tuscany SCA 1.0 release, was: SCA 0.92 release?

[snip]
>> Bringing this thread up again as time is ticking on if we want to get a
>> release out this month. How would people feel about taking a branch for this
>> release in a bit less than 2 weeks, say aiming for the 14/15th of August?
>> That should just about give enough time for clean up and voting to get a
>> release out by the end of  August.
>>
>> Another thing I wondered about was the name, we've been talking about this
>> being 0.92, how about something higher to show we're getting closer, maybe
>> 0.95 or 0.98 or even 0.99? (that prompts a what/when is 1.0, I'll start a
>> separate thread about that)
>>
>>    ...ant
>>     

What/when is 1.0? Good question :) There has been a lot of progress in 
the recent 0.90 and 0.91 releases and I agree that Tuscany SCA is 
getting close to a 1.0 release.

So, let's start discussing "What is Tuscany 1.0". I'm moving this thread 
to the tuscany-user list as I'd like to get feedback, requests and ideas 
from Tuscany users.

Speaking for myself, here's some thoughts on what I'm interested in 
having in a 1.0 release:

* SCA assembly spec 1.0 support
Looks close to complete here, I think it just needs a little more 
testing and a simple implementation of a distributed domain. Simon seems 
to be making good progress in that area. Also I'd like to have a simple 
admin console to add/remove contributions and composites and allocate 
components to nodes.

* SCA Policy framework 1.0
Modules policy and policy-xml are taking shape. Having one concrete 
policy like Security implemented on top the framework would be good. 
Maybe Venkat could give his thoughts on this?

* Extension points for component implementations, bindings, databindings 
and policies
SPIs need a little cleanup as they're starting to carry a number of 
deprecated interfaces/methods. There's no extensibility mechanism for 
policies yet but it shouldn't be too hard to add that with a pattern 
similar to the existing extension points.

* SCA Java APIs and Annotations 1.0
Almost complete, just missing a complete implementation of 
ServiceReferences and a few conversational annotations. I'd like to 
refine the SCADomain.getService() API too. Also, on a separate but 
related note, a better Java proxy (better than a JDK proxy) would be 
great, I've seen a Cglib proxy contributed recently, how about extending 
that idea to all proxies?

* Spring component implementation
This looks in a good shape. Mike, what else are you planning to do there?

* WS binding
What is left to do? The SCA Java Releases wiki page lists some work 
items in this space, which ones do people think should be done for a 1.0 
release?

* JMS binding
Seems to partly work but will need a little more to align with the 
latest spec. Anybody interested in helping with it?

* Feed and JSON bindings
IMO important to have to integrate with Web 2.0 apps. The Feed binding 
is fine as far as I can tell. What do people think remains to be done 
for the JSON binding?

* Scripting component implementation
I've been a happy user of <implementation.script> but have not tried 
using complex types and much integration with bindings. What's left to 
be done here?

* Geronimo integration
I'd like to be able to deploy SCA contributions to Geronimo, looks like 
there's good progress on that front. I'd also like to support the 
integration of Webapps in SCA compositions as <implementation.web> 
components.

* Docs
Our architecture docs could use some improvements and cleanup :). For 
user docs, what do people think about developing more tutorials and 
variations around the Online Store tutorial?

* Samples
Some of them need minor cleanup. Are we missing samples in any specific 
area?

* Other implementation and binding extensions
We have starters or partial support for <implementation.notification>, 
<implementation.bpel>, <binding.ejb>, <binding.rmi>, 
<implementation.osgi>. Could people help get these extensions in the 
release?

Thoughts? Anything people would like to discuss and get included in 
Tuscany SCA 1.0, please bring it up...

--
Jean-Sebastien


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org


Re: Contents of Tuscany SCA 1.0 release, was: SCA 0.92 release?

Posted by Radim Kolarik <ra...@googlemail.com>.
Hi Simon,

thank you very much for your answer. Our project deadline is quickly
approaching and we have decided to go with POJOs for the time being,
as it seems that there is a wider POJO based web service support at
the moment (including available tooling). For future versions, we will
most likely consider SDOs as well.

Best regards,
Radim

On 8/8/07, Simon Nash <na...@hursley.ibm.com> wrote:
> Hi Radim,
> It's great to get your feedback on this.  Your posts to the user list
> (including those with "tough" questions, like Java2WSDL and "on the fly"
> WSDL generation :-) have been much appreciated.
>
> I am currently working on asynchronous support for callbacks.
> The @OneWay part of async is already working in the current trunk and
> we just need a test case for it, which I will add when I have got
> callbacks into reasonable shape.  At the moment I am working on
> TUSCANY-1496 which will greatly simplify the callback implementation
> by treating callbacks almost identically to forward calls both within
> the core framework and within binding extensions.  I am also looking
> at TUSCANY-1347 and TUSCANY-1500 which relate to slightly more advanced
> use cases for callbacks including some gaps in our support for the
> full Java API for callbacks.
>
> Callbacks and conversations are intimately connected and SimonL and I
> have had one discussion about this and some of the spec points that are
> not 100% clear.  I'm expecting to work with SimonL to bring together
> his work on conversations with my work on callbacks, and to have full
> support in the 1.0 release for both callbacks and conversations (and
> the interactions between them).  This support would include the core
> framework as well as the Web Service binding.
>
> After this is all taken care of, I would be very interested in putting
> together a sample of the type that you describe with complex POJO types
> (which I would like to represent as SDOs) and Web Services.  This would
> require getting the SDO tooling story sorted as well.  Of course,
> someone else might get to this one ahead of me :-)  I would be interested
> to know whether this would meet your requirement, or whether you are
> specifically looking to pass around non-SDO POJOs.
>
>   Simon
>
> Radim Kolarik wrote:
>
> > Hi Ant,
> >
> > the top priority regarding web services would be having "on fly"
> > generation of WSDL, without the need of having to supply own file.
> > Axis2 can do it for its services described in services.xml file. It
> > would also help if there was a working example that would use complex
> > POJO types as parameters and results of a service call, deployed as a
> > web service, as I am struggling to make this work. It is not clear to
> > me if I need to supply services.xml or not for Axis to make complex
> > types working (register serializers/deserializers).
> >
> > Also important are following items in your list, however, not as
> > important as the above issues. The items are ordered by priority.
> >
> > - WS Security
> > - Sort out our WSDL tooling story - get SDO integrated into Axis2?
> > - asynchronous services
> > - conversational services
> >
> > Thanks a lot!
> > Radim
> >
> > On 8/7/07, ant elder <an...@gmail.com> wrote:
> >
> >>http://cwiki.apache.org/confluence/display/TUSCANYWIKI/SCA+Java+Next+Release+Contents<http://cwiki.apache.org/confluence/display/TUSCANYWIKI/SCA+Java+Next+Release+Contents>
> >>
> >>Note that its likely we wont have time to get everything listed there done
> >>in 1.0 so please say which things are important to you to help us prioritize
> >>what does get done.
> >>
> >>  ...ant
> >>
> >>On 8/7/07, Radim Kolarik < radim.list@googlemail.com> wrote:
> >>
> >>>Hi Jean-Sebastien,
> >>>
> >>>where is the SCA Java Releases wiki page which lists some work
> >>>items in ws binding space, that you mentioned?
> >>>
> >>>Thanks,
> >>>Radim
> >>>
> >>>On 8/6/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> >>>
> >>>>[snip]
> >>>>
> >>>>>>Bringing this thread up again as time is ticking on if we want to get
> >>>
> >>>a
> >>>
> >>>>>>release out this month. How would people feel about taking a branch
> >>>
> >>>for this
> >>>
> >>>>>>release in a bit less than 2 weeks, say aiming for the 14/15th of
> >>>
> >>>August?
> >>>
> >>>>>>That should just about give enough time for clean up and voting to
> >>>
> >>>get a
> >>>
> >>>>>>release out by the end of  August.
> >>>>>>
> >>>>>>Another thing I wondered about was the name, we've been talking about
> >>>
> >>>this
> >>>
> >>>>>>being 0.92, how about something higher to show we're getting closer,
> >>>
> >>>maybe
> >>>
> >>>>>>0.95 or 0.98 or even 0.99? (that prompts a what/when is 1.0, I'll
> >>>
> >>>start a
> >>>
> >>>>>>separate thread about that)
> >>>>>>
> >>>>>>   ...ant
> >>>>>>
> >>>>
> >>>>What/when is 1.0? Good question :) There has been a lot of progress in
> >>>>the recent 0.90 and 0.91 releases and I agree that Tuscany SCA is
> >>>>getting close to a 1.0 release.
> >>>>
> >>>>So, let's start discussing "What is Tuscany 1.0". I'm moving this thread
> >>>>to the tuscany-user list as I'd like to get feedback, requests and ideas
> >>>>from Tuscany users.
> >>>>
> >>>>Speaking for myself, here's some thoughts on what I'm interested in
> >>>>having in a 1.0 release:
> >>>>
> >>>>* SCA assembly spec 1.0 support
> >>>>Looks close to complete here, I think it just needs a little more
> >>>>testing and a simple implementation of a distributed domain. Simon seems
> >>>
> >>>>to be making good progress in that area. Also I'd like to have a simple
> >>>>admin console to add/remove contributions and composites and allocate
> >>>>components to nodes.
> >>>>
> >>>>* SCA Policy framework 1.0
> >>>>Modules policy and policy-xml are taking shape. Having one concrete
> >>>>policy like Security implemented on top the framework would be good.
> >>>>Maybe Venkat could give his thoughts on this?
> >>>>
> >>>>* Extension points for component implementations, bindings, databindings
> >>>>and policies
> >>>>SPIs need a little cleanup as they're starting to carry a number of
> >>>>deprecated interfaces/methods. There's no extensibility mechanism for
> >>>>policies yet but it shouldn't be too hard to add that with a pattern
> >>>>similar to the existing extension points.
> >>>>
> >>>>* SCA Java APIs and Annotations 1.0
> >>>>Almost complete, just missing a complete implementation of
> >>>>ServiceReferences and a few conversational annotations. I'd like to
> >>>>refine the SCADomain.getService() API too. Also, on a separate but
> >>>>related note, a better Java proxy (better than a JDK proxy) would be
> >>>>great, I've seen a Cglib proxy contributed recently, how about extending
> >>>>that idea to all proxies?
> >>>>
> >>>>* Spring component implementation
> >>>>This looks in a good shape. Mike, what else are you planning to do
> >>>
> >>>there?
> >>>
> >>>>* WS binding
> >>>>What is left to do? The SCA Java Releases wiki page lists some work
> >>>>items in this space, which ones do people think should be done for a 1.0
> >>>>release?
> >>>>
> >>>>* JMS binding
> >>>>Seems to partly work but will need a little more to align with the
> >>>>latest spec. Anybody interested in helping with it?
> >>>>
> >>>>* Feed and JSON bindings
> >>>>IMO important to have to integrate with Web 2.0 apps. The Feed binding
> >>>>is fine as far as I can tell. What do people think remains to be done
> >>>>for the JSON binding?
> >>>>
> >>>>* Scripting component implementation
> >>>>I've been a happy user of < implementation.script> but have not tried
> >>>>using complex types and much integration with bindings. What's left to
> >>>>be done here?
> >>>>
> >>>>* Geronimo integration
> >>>>I'd like to be able to deploy SCA contributions to Geronimo, looks like
> >>>>there's good progress on that front. I'd also like to support the
> >>>>integration of Webapps in SCA compositions as <implementation.web>
> >>>>components.
> >>>>
> >>>>* Docs
> >>>>Our architecture docs could use some improvements and cleanup :). For
> >>>>user docs, what do people think about developing more tutorials and
> >>>>variations around the Online Store tutorial?
> >>>>
> >>>>* Samples
> >>>>Some of them need minor cleanup. Are we missing samples in any specific
> >>>>area?
> >>>>
> >>>>* Other implementation and binding extensions
> >>>>We have starters or partial support for <implementation.notification>,
> >>>><implementation.bpel>, <binding.ejb>, < binding.rmi>,
> >>>><implementation.osgi>. Could people help get these extensions in the
> >>>>release?
> >>>>
> >>>>Thoughts? Anything people would like to discuss and get included in
> >>>>Tuscany SCA 1.0, please bring it up...
> >>>>
> >>>>--
> >>>>Jean-Sebastien
> >>>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-user-help@ws.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org


Re: Contents of Tuscany SCA 1.0 release, was: SCA 0.92 release?

Posted by Simon Nash <na...@hursley.ibm.com>.
Hi Radim,
It's great to get your feedback on this.  Your posts to the user list
(including those with "tough" questions, like Java2WSDL and "on the fly"
WSDL generation :-) have been much appreciated.

I am currently working on asynchronous support for callbacks.
The @OneWay part of async is already working in the current trunk and
we just need a test case for it, which I will add when I have got
callbacks into reasonable shape.  At the moment I am working on
TUSCANY-1496 which will greatly simplify the callback implementation
by treating callbacks almost identically to forward calls both within
the core framework and within binding extensions.  I am also looking
at TUSCANY-1347 and TUSCANY-1500 which relate to slightly more advanced
use cases for callbacks including some gaps in our support for the
full Java API for callbacks.

Callbacks and conversations are intimately connected and SimonL and I
have had one discussion about this and some of the spec points that are
not 100% clear.  I'm expecting to work with SimonL to bring together
his work on conversations with my work on callbacks, and to have full
support in the 1.0 release for both callbacks and conversations (and
the interactions between them).  This support would include the core
framework as well as the Web Service binding.

After this is all taken care of, I would be very interested in putting
together a sample of the type that you describe with complex POJO types
(which I would like to represent as SDOs) and Web Services.  This would
require getting the SDO tooling story sorted as well.  Of course,
someone else might get to this one ahead of me :-)  I would be interested
to know whether this would meet your requirement, or whether you are
specifically looking to pass around non-SDO POJOs.

   Simon

Radim Kolarik wrote:

> Hi Ant,
> 
> the top priority regarding web services would be having "on fly"
> generation of WSDL, without the need of having to supply own file.
> Axis2 can do it for its services described in services.xml file. It
> would also help if there was a working example that would use complex
> POJO types as parameters and results of a service call, deployed as a
> web service, as I am struggling to make this work. It is not clear to
> me if I need to supply services.xml or not for Axis to make complex
> types working (register serializers/deserializers).
> 
> Also important are following items in your list, however, not as
> important as the above issues. The items are ordered by priority.
> 
> - WS Security
> - Sort out our WSDL tooling story - get SDO integrated into Axis2?
> - asynchronous services
> - conversational services
> 
> Thanks a lot!
> Radim
> 
> On 8/7/07, ant elder <an...@gmail.com> wrote:
> 
>>http://cwiki.apache.org/confluence/display/TUSCANYWIKI/SCA+Java+Next+Release+Contents<http://cwiki.apache.org/confluence/display/TUSCANYWIKI/SCA+Java+Next+Release+Contents>
>>
>>Note that its likely we wont have time to get everything listed there done
>>in 1.0 so please say which things are important to you to help us prioritize
>>what does get done.
>>
>>  ...ant
>>
>>On 8/7/07, Radim Kolarik < radim.list@googlemail.com> wrote:
>>
>>>Hi Jean-Sebastien,
>>>
>>>where is the SCA Java Releases wiki page which lists some work
>>>items in ws binding space, that you mentioned?
>>>
>>>Thanks,
>>>Radim
>>>
>>>On 8/6/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>>>
>>>>[snip]
>>>>
>>>>>>Bringing this thread up again as time is ticking on if we want to get
>>>
>>>a
>>>
>>>>>>release out this month. How would people feel about taking a branch
>>>
>>>for this
>>>
>>>>>>release in a bit less than 2 weeks, say aiming for the 14/15th of
>>>
>>>August?
>>>
>>>>>>That should just about give enough time for clean up and voting to
>>>
>>>get a
>>>
>>>>>>release out by the end of  August.
>>>>>>
>>>>>>Another thing I wondered about was the name, we've been talking about
>>>
>>>this
>>>
>>>>>>being 0.92, how about something higher to show we're getting closer,
>>>
>>>maybe
>>>
>>>>>>0.95 or 0.98 or even 0.99? (that prompts a what/when is 1.0, I'll
>>>
>>>start a
>>>
>>>>>>separate thread about that)
>>>>>>
>>>>>>   ...ant
>>>>>>
>>>>
>>>>What/when is 1.0? Good question :) There has been a lot of progress in
>>>>the recent 0.90 and 0.91 releases and I agree that Tuscany SCA is
>>>>getting close to a 1.0 release.
>>>>
>>>>So, let's start discussing "What is Tuscany 1.0". I'm moving this thread
>>>>to the tuscany-user list as I'd like to get feedback, requests and ideas
>>>>from Tuscany users.
>>>>
>>>>Speaking for myself, here's some thoughts on what I'm interested in
>>>>having in a 1.0 release:
>>>>
>>>>* SCA assembly spec 1.0 support
>>>>Looks close to complete here, I think it just needs a little more
>>>>testing and a simple implementation of a distributed domain. Simon seems
>>>
>>>>to be making good progress in that area. Also I'd like to have a simple
>>>>admin console to add/remove contributions and composites and allocate
>>>>components to nodes.
>>>>
>>>>* SCA Policy framework 1.0
>>>>Modules policy and policy-xml are taking shape. Having one concrete
>>>>policy like Security implemented on top the framework would be good.
>>>>Maybe Venkat could give his thoughts on this?
>>>>
>>>>* Extension points for component implementations, bindings, databindings
>>>>and policies
>>>>SPIs need a little cleanup as they're starting to carry a number of
>>>>deprecated interfaces/methods. There's no extensibility mechanism for
>>>>policies yet but it shouldn't be too hard to add that with a pattern
>>>>similar to the existing extension points.
>>>>
>>>>* SCA Java APIs and Annotations 1.0
>>>>Almost complete, just missing a complete implementation of
>>>>ServiceReferences and a few conversational annotations. I'd like to
>>>>refine the SCADomain.getService() API too. Also, on a separate but
>>>>related note, a better Java proxy (better than a JDK proxy) would be
>>>>great, I've seen a Cglib proxy contributed recently, how about extending
>>>>that idea to all proxies?
>>>>
>>>>* Spring component implementation
>>>>This looks in a good shape. Mike, what else are you planning to do
>>>
>>>there?
>>>
>>>>* WS binding
>>>>What is left to do? The SCA Java Releases wiki page lists some work
>>>>items in this space, which ones do people think should be done for a 1.0
>>>>release?
>>>>
>>>>* JMS binding
>>>>Seems to partly work but will need a little more to align with the
>>>>latest spec. Anybody interested in helping with it?
>>>>
>>>>* Feed and JSON bindings
>>>>IMO important to have to integrate with Web 2.0 apps. The Feed binding
>>>>is fine as far as I can tell. What do people think remains to be done
>>>>for the JSON binding?
>>>>
>>>>* Scripting component implementation
>>>>I've been a happy user of < implementation.script> but have not tried
>>>>using complex types and much integration with bindings. What's left to
>>>>be done here?
>>>>
>>>>* Geronimo integration
>>>>I'd like to be able to deploy SCA contributions to Geronimo, looks like
>>>>there's good progress on that front. I'd also like to support the
>>>>integration of Webapps in SCA compositions as <implementation.web>
>>>>components.
>>>>
>>>>* Docs
>>>>Our architecture docs could use some improvements and cleanup :). For
>>>>user docs, what do people think about developing more tutorials and
>>>>variations around the Online Store tutorial?
>>>>
>>>>* Samples
>>>>Some of them need minor cleanup. Are we missing samples in any specific
>>>>area?
>>>>
>>>>* Other implementation and binding extensions
>>>>We have starters or partial support for <implementation.notification>,
>>>><implementation.bpel>, <binding.ejb>, < binding.rmi>,
>>>><implementation.osgi>. Could people help get these extensions in the
>>>>release?
>>>>
>>>>Thoughts? Anything people would like to discuss and get included in
>>>>Tuscany SCA 1.0, please bring it up...
>>>>
>>>>--
>>>>Jean-Sebastien
>>>>



---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org


Re: Contents of Tuscany SCA 1.0 release, was: SCA 0.92 release?

Posted by Radim Kolarik <ra...@googlemail.com>.
Hi Ant,

the top priority regarding web services would be having "on fly"
generation of WSDL, without the need of having to supply own file.
Axis2 can do it for its services described in services.xml file. It
would also help if there was a working example that would use complex
POJO types as parameters and results of a service call, deployed as a
web service, as I am struggling to make this work. It is not clear to
me if I need to supply services.xml or not for Axis to make complex
types working (register serializers/deserializers).

Also important are following items in your list, however, not as
important as the above issues. The items are ordered by priority.

- WS Security
- Sort out our WSDL tooling story - get SDO integrated into Axis2?
- asynchronous services
- conversational services

Thanks a lot!
Radim

On 8/7/07, ant elder <an...@gmail.com> wrote:
> http://cwiki.apache.org/confluence/display/TUSCANYWIKI/SCA+Java+Next+Release+Contents<http://cwiki.apache.org/confluence/display/TUSCANYWIKI/SCA+Java+Next+Release+Contents>
>
> Note that its likely we wont have time to get everything listed there done
> in 1.0 so please say which things are important to you to help us prioritize
> what does get done.
>
>   ...ant
>
> On 8/7/07, Radim Kolarik < radim.list@googlemail.com> wrote:
> >
> > Hi Jean-Sebastien,
> >
> > where is the SCA Java Releases wiki page which lists some work
> > items in ws binding space, that you mentioned?
> >
> > Thanks,
> > Radim
> >
> > On 8/6/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> > > [snip]
> > > >> Bringing this thread up again as time is ticking on if we want to get
> > a
> > > >> release out this month. How would people feel about taking a branch
> > for this
> > > >> release in a bit less than 2 weeks, say aiming for the 14/15th of
> > August?
> > > >> That should just about give enough time for clean up and voting to
> > get a
> > > >> release out by the end of  August.
> > > >>
> > > >> Another thing I wondered about was the name, we've been talking about
> > this
> > > >> being 0.92, how about something higher to show we're getting closer,
> > maybe
> > > >> 0.95 or 0.98 or even 0.99? (that prompts a what/when is 1.0, I'll
> > start a
> > > >> separate thread about that)
> > > >>
> > > >>    ...ant
> > > >>
> > >
> > > What/when is 1.0? Good question :) There has been a lot of progress in
> > > the recent 0.90 and 0.91 releases and I agree that Tuscany SCA is
> > > getting close to a 1.0 release.
> > >
> > > So, let's start discussing "What is Tuscany 1.0". I'm moving this thread
> > > to the tuscany-user list as I'd like to get feedback, requests and ideas
> > > from Tuscany users.
> > >
> > > Speaking for myself, here's some thoughts on what I'm interested in
> > > having in a 1.0 release:
> > >
> > > * SCA assembly spec 1.0 support
> > > Looks close to complete here, I think it just needs a little more
> > > testing and a simple implementation of a distributed domain. Simon seems
> >
> > > to be making good progress in that area. Also I'd like to have a simple
> > > admin console to add/remove contributions and composites and allocate
> > > components to nodes.
> > >
> > > * SCA Policy framework 1.0
> > > Modules policy and policy-xml are taking shape. Having one concrete
> > > policy like Security implemented on top the framework would be good.
> > > Maybe Venkat could give his thoughts on this?
> > >
> > > * Extension points for component implementations, bindings, databindings
> > > and policies
> > > SPIs need a little cleanup as they're starting to carry a number of
> > > deprecated interfaces/methods. There's no extensibility mechanism for
> > > policies yet but it shouldn't be too hard to add that with a pattern
> > > similar to the existing extension points.
> > >
> > > * SCA Java APIs and Annotations 1.0
> > > Almost complete, just missing a complete implementation of
> > > ServiceReferences and a few conversational annotations. I'd like to
> > > refine the SCADomain.getService() API too. Also, on a separate but
> > > related note, a better Java proxy (better than a JDK proxy) would be
> > > great, I've seen a Cglib proxy contributed recently, how about extending
> > > that idea to all proxies?
> > >
> > > * Spring component implementation
> > > This looks in a good shape. Mike, what else are you planning to do
> > there?
> > >
> > > * WS binding
> > > What is left to do? The SCA Java Releases wiki page lists some work
> > > items in this space, which ones do people think should be done for a 1.0
> > > release?
> > >
> > > * JMS binding
> > > Seems to partly work but will need a little more to align with the
> > > latest spec. Anybody interested in helping with it?
> > >
> > > * Feed and JSON bindings
> > > IMO important to have to integrate with Web 2.0 apps. The Feed binding
> > > is fine as far as I can tell. What do people think remains to be done
> > > for the JSON binding?
> > >
> > > * Scripting component implementation
> > > I've been a happy user of < implementation.script> but have not tried
> > > using complex types and much integration with bindings. What's left to
> > > be done here?
> > >
> > > * Geronimo integration
> > > I'd like to be able to deploy SCA contributions to Geronimo, looks like
> > > there's good progress on that front. I'd also like to support the
> > > integration of Webapps in SCA compositions as <implementation.web>
> > > components.
> > >
> > > * Docs
> > > Our architecture docs could use some improvements and cleanup :). For
> > > user docs, what do people think about developing more tutorials and
> > > variations around the Online Store tutorial?
> > >
> > > * Samples
> > > Some of them need minor cleanup. Are we missing samples in any specific
> > > area?
> > >
> > > * Other implementation and binding extensions
> > > We have starters or partial support for <implementation.notification>,
> > > <implementation.bpel>, <binding.ejb>, < binding.rmi>,
> > > <implementation.osgi>. Could people help get these extensions in the
> > > release?
> > >
> > > Thoughts? Anything people would like to discuss and get included in
> > > Tuscany SCA 1.0, please bring it up...
> > >
> > > --
> > > Jean-Sebastien
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: tuscany-user-help@ws.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-user-help@ws.apache.org
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org


Re: Contents of Tuscany SCA 1.0 release, was: SCA 0.92 release?

Posted by ant elder <an...@gmail.com>.
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/SCA+Java+Next+Release+Contents<http://cwiki.apache.org/confluence/display/TUSCANYWIKI/SCA+Java+Next+Release+Contents>

Note that its likely we wont have time to get everything listed there done
in 1.0 so please say which things are important to you to help us prioritize
what does get done.

   ...ant

On 8/7/07, Radim Kolarik < radim.list@googlemail.com> wrote:
>
> Hi Jean-Sebastien,
>
> where is the SCA Java Releases wiki page which lists some work
> items in ws binding space, that you mentioned?
>
> Thanks,
> Radim
>
> On 8/6/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> > [snip]
> > >> Bringing this thread up again as time is ticking on if we want to get
> a
> > >> release out this month. How would people feel about taking a branch
> for this
> > >> release in a bit less than 2 weeks, say aiming for the 14/15th of
> August?
> > >> That should just about give enough time for clean up and voting to
> get a
> > >> release out by the end of  August.
> > >>
> > >> Another thing I wondered about was the name, we've been talking about
> this
> > >> being 0.92, how about something higher to show we're getting closer,
> maybe
> > >> 0.95 or 0.98 or even 0.99? (that prompts a what/when is 1.0, I'll
> start a
> > >> separate thread about that)
> > >>
> > >>    ...ant
> > >>
> >
> > What/when is 1.0? Good question :) There has been a lot of progress in
> > the recent 0.90 and 0.91 releases and I agree that Tuscany SCA is
> > getting close to a 1.0 release.
> >
> > So, let's start discussing "What is Tuscany 1.0". I'm moving this thread
> > to the tuscany-user list as I'd like to get feedback, requests and ideas
> > from Tuscany users.
> >
> > Speaking for myself, here's some thoughts on what I'm interested in
> > having in a 1.0 release:
> >
> > * SCA assembly spec 1.0 support
> > Looks close to complete here, I think it just needs a little more
> > testing and a simple implementation of a distributed domain. Simon seems
>
> > to be making good progress in that area. Also I'd like to have a simple
> > admin console to add/remove contributions and composites and allocate
> > components to nodes.
> >
> > * SCA Policy framework 1.0
> > Modules policy and policy-xml are taking shape. Having one concrete
> > policy like Security implemented on top the framework would be good.
> > Maybe Venkat could give his thoughts on this?
> >
> > * Extension points for component implementations, bindings, databindings
> > and policies
> > SPIs need a little cleanup as they're starting to carry a number of
> > deprecated interfaces/methods. There's no extensibility mechanism for
> > policies yet but it shouldn't be too hard to add that with a pattern
> > similar to the existing extension points.
> >
> > * SCA Java APIs and Annotations 1.0
> > Almost complete, just missing a complete implementation of
> > ServiceReferences and a few conversational annotations. I'd like to
> > refine the SCADomain.getService() API too. Also, on a separate but
> > related note, a better Java proxy (better than a JDK proxy) would be
> > great, I've seen a Cglib proxy contributed recently, how about extending
> > that idea to all proxies?
> >
> > * Spring component implementation
> > This looks in a good shape. Mike, what else are you planning to do
> there?
> >
> > * WS binding
> > What is left to do? The SCA Java Releases wiki page lists some work
> > items in this space, which ones do people think should be done for a 1.0
> > release?
> >
> > * JMS binding
> > Seems to partly work but will need a little more to align with the
> > latest spec. Anybody interested in helping with it?
> >
> > * Feed and JSON bindings
> > IMO important to have to integrate with Web 2.0 apps. The Feed binding
> > is fine as far as I can tell. What do people think remains to be done
> > for the JSON binding?
> >
> > * Scripting component implementation
> > I've been a happy user of < implementation.script> but have not tried
> > using complex types and much integration with bindings. What's left to
> > be done here?
> >
> > * Geronimo integration
> > I'd like to be able to deploy SCA contributions to Geronimo, looks like
> > there's good progress on that front. I'd also like to support the
> > integration of Webapps in SCA compositions as <implementation.web>
> > components.
> >
> > * Docs
> > Our architecture docs could use some improvements and cleanup :). For
> > user docs, what do people think about developing more tutorials and
> > variations around the Online Store tutorial?
> >
> > * Samples
> > Some of them need minor cleanup. Are we missing samples in any specific
> > area?
> >
> > * Other implementation and binding extensions
> > We have starters or partial support for <implementation.notification>,
> > <implementation.bpel>, <binding.ejb>, < binding.rmi>,
> > <implementation.osgi>. Could people help get these extensions in the
> > release?
> >
> > Thoughts? Anything people would like to discuss and get included in
> > Tuscany SCA 1.0, please bring it up...
> >
> > --
> > Jean-Sebastien
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-user-help@ws.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-user-help@ws.apache.org
>
>

Re: Contents of Tuscany SCA 1.0 release, was: SCA 0.92 release?

Posted by Radim Kolarik <ra...@googlemail.com>.
Hi Jean-Sebastien,

where is the SCA Java Releases wiki page which lists some work
items in ws binding space, that you mentioned?

Thanks,
Radim

On 8/6/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> [snip]
> >> Bringing this thread up again as time is ticking on if we want to get a
> >> release out this month. How would people feel about taking a branch for this
> >> release in a bit less than 2 weeks, say aiming for the 14/15th of August?
> >> That should just about give enough time for clean up and voting to get a
> >> release out by the end of  August.
> >>
> >> Another thing I wondered about was the name, we've been talking about this
> >> being 0.92, how about something higher to show we're getting closer, maybe
> >> 0.95 or 0.98 or even 0.99? (that prompts a what/when is 1.0, I'll start a
> >> separate thread about that)
> >>
> >>    ...ant
> >>
>
> What/when is 1.0? Good question :) There has been a lot of progress in
> the recent 0.90 and 0.91 releases and I agree that Tuscany SCA is
> getting close to a 1.0 release.
>
> So, let's start discussing "What is Tuscany 1.0". I'm moving this thread
> to the tuscany-user list as I'd like to get feedback, requests and ideas
> from Tuscany users.
>
> Speaking for myself, here's some thoughts on what I'm interested in
> having in a 1.0 release:
>
> * SCA assembly spec 1.0 support
> Looks close to complete here, I think it just needs a little more
> testing and a simple implementation of a distributed domain. Simon seems
> to be making good progress in that area. Also I'd like to have a simple
> admin console to add/remove contributions and composites and allocate
> components to nodes.
>
> * SCA Policy framework 1.0
> Modules policy and policy-xml are taking shape. Having one concrete
> policy like Security implemented on top the framework would be good.
> Maybe Venkat could give his thoughts on this?
>
> * Extension points for component implementations, bindings, databindings
> and policies
> SPIs need a little cleanup as they're starting to carry a number of
> deprecated interfaces/methods. There's no extensibility mechanism for
> policies yet but it shouldn't be too hard to add that with a pattern
> similar to the existing extension points.
>
> * SCA Java APIs and Annotations 1.0
> Almost complete, just missing a complete implementation of
> ServiceReferences and a few conversational annotations. I'd like to
> refine the SCADomain.getService() API too. Also, on a separate but
> related note, a better Java proxy (better than a JDK proxy) would be
> great, I've seen a Cglib proxy contributed recently, how about extending
> that idea to all proxies?
>
> * Spring component implementation
> This looks in a good shape. Mike, what else are you planning to do there?
>
> * WS binding
> What is left to do? The SCA Java Releases wiki page lists some work
> items in this space, which ones do people think should be done for a 1.0
> release?
>
> * JMS binding
> Seems to partly work but will need a little more to align with the
> latest spec. Anybody interested in helping with it?
>
> * Feed and JSON bindings
> IMO important to have to integrate with Web 2.0 apps. The Feed binding
> is fine as far as I can tell. What do people think remains to be done
> for the JSON binding?
>
> * Scripting component implementation
> I've been a happy user of <implementation.script> but have not tried
> using complex types and much integration with bindings. What's left to
> be done here?
>
> * Geronimo integration
> I'd like to be able to deploy SCA contributions to Geronimo, looks like
> there's good progress on that front. I'd also like to support the
> integration of Webapps in SCA compositions as <implementation.web>
> components.
>
> * Docs
> Our architecture docs could use some improvements and cleanup :). For
> user docs, what do people think about developing more tutorials and
> variations around the Online Store tutorial?
>
> * Samples
> Some of them need minor cleanup. Are we missing samples in any specific
> area?
>
> * Other implementation and binding extensions
> We have starters or partial support for <implementation.notification>,
> <implementation.bpel>, <binding.ejb>, <binding.rmi>,
> <implementation.osgi>. Could people help get these extensions in the
> release?
>
> Thoughts? Anything people would like to discuss and get included in
> Tuscany SCA 1.0, please bring it up...
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-user-help@ws.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org


Re: Contents of Tuscany SCA 1.0 release, was: SCA 0.92 release?

Posted by Simon Laws <si...@googlemail.com>.
On 8/6/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
> [snip]
> >> Bringing this thread up again as time is ticking on if we want to get a
> >> release out this month. How would people feel about taking a branch for
> this
> >> release in a bit less than 2 weeks, say aiming for the 14/15th of
> August?
> >> That should just about give enough time for clean up and voting to get
> a
> >> release out by the end of  August.
> >>
> >> Another thing I wondered about was the name, we've been talking about
> this
> >> being 0.92, how about something higher to show we're getting closer,
> maybe
> >> 0.95 or 0.98 or even 0.99? (that prompts a what/when is 1.0, I'll start
> a
> >> separate thread about that)
> >>
> >>    ...ant
> >>
>
> What/when is 1.0? Good question :) There has been a lot of progress in
> the recent 0.90 and 0.91 releases and I agree that Tuscany SCA is
> getting close to a 1.0 release.
>
> So, let's start discussing "What is Tuscany 1.0". I'm moving this thread
> to the tuscany-user list as I'd like to get feedback, requests and ideas
> from Tuscany users.
>
> Speaking for myself, here's some thoughts on what I'm interested in
> having in a 1.0 release:
>
> * SCA assembly spec 1.0 support
> Looks close to complete here, I think it just needs a little more
> testing and a simple implementation of a distributed domain. Simon seems
> to be making good progress in that area. Also I'd like to have a simple
> admin console to add/remove contributions and composites and allocate
> components to nodes.
>
> * SCA Policy framework 1.0
> Modules policy and policy-xml are taking shape. Having one concrete
> policy like Security implemented on top the framework would be good.
> Maybe Venkat could give his thoughts on this?
>
> * Extension points for component implementations, bindings, databindings
> and policies
> SPIs need a little cleanup as they're starting to carry a number of
> deprecated interfaces/methods. There's no extensibility mechanism for
> policies yet but it shouldn't be too hard to add that with a pattern
> similar to the existing extension points.
>
> * SCA Java APIs and Annotations 1.0
> Almost complete, just missing a complete implementation of
> ServiceReferences and a few conversational annotations. I'd like to
> refine the SCADomain.getService() API too. Also, on a separate but
> related note, a better Java proxy (better than a JDK proxy) would be
> great, I've seen a Cglib proxy contributed recently, how about extending
> that idea to all proxies?
>
> * Spring component implementation
> This looks in a good shape. Mike, what else are you planning to do there?
>
> * WS binding
> What is left to do? The SCA Java Releases wiki page lists some work
> items in this space, which ones do people think should be done for a 1.0
> release?
>
> * JMS binding
> Seems to partly work but will need a little more to align with the
> latest spec. Anybody interested in helping with it?
>
> * Feed and JSON bindings
> IMO important to have to integrate with Web 2.0 apps. The Feed binding
> is fine as far as I can tell. What do people think remains to be done
> for the JSON binding?
>
> * Scripting component implementation
> I've been a happy user of <implementation.script> but have not tried
> using complex types and much integration with bindings. What's left to
> be done here?
>
> * Geronimo integration
> I'd like to be able to deploy SCA contributions to Geronimo, looks like
> there's good progress on that front. I'd also like to support the
> integration of Webapps in SCA compositions as <implementation.web>
> components.
>
> * Docs
> Our architecture docs could use some improvements and cleanup :). For
> user docs, what do people think about developing more tutorials and
> variations around the Online Store tutorial?
>
> * Samples
> Some of them need minor cleanup. Are we missing samples in any specific
> area?
>
> * Other implementation and binding extensions
> We have starters or partial support for <implementation.notification>,
> <implementation.bpel>, <binding.ejb>, <binding.rmi>,
> <implementation.osgi>. Could people help get these extensions in the
> release?
>
> Thoughts? Anything people would like to discuss and get included in
> Tuscany SCA 1.0, please bring it up...
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-user-help@ws.apache.org
>
>
Hi Sebastien, a couple of things from my point of view.

Re.

* SCA Java APIs and Annotations 1.0
Almost complete, just missing a complete implementation of
ServiceReferences and a few conversational annotations.

I just opened https://issues.apache.org/jira/browse/TUSCANY-1511 to bring
forward the conversational issues that were recorded as we went through the
spec/code a couple of weeks ago. The major parts here are tied up with the
overlap between callbacks and conversations which I know the other Simon has
been looking at in detail and on the service reference piece which you
already mention. Happy to help out with these parts but want to draw a line
under the distributed support first.

The other thing that I think we need to add to the list is a diagnostics and
error handling story. There was a thread on it ages ago but we didn't do
anything about it. I'll go look it up and restart it.

Simon

Re: Contents of Tuscany SCA 1.0 release, was: SCA 0.92 release?

Posted by ant elder <an...@gmail.com>.
On 8/6/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
> [snip]
> >> Bringing this thread up again as time is ticking on if we want to get a
> >> release out this month. How would people feel about taking a branch for
> this
> >> release in a bit less than 2 weeks, say aiming for the 14/15th of
> August?
> >> That should just about give enough time for clean up and voting to get
> a
> >> release out by the end of  August.
> >>
> >> Another thing I wondered about was the name, we've been talking about
> this
> >> being 0.92, how about something higher to show we're getting closer,
> maybe
> >> 0.95 or 0.98 or even 0.99? (that prompts a what/when is 1.0, I'll start
> a
> >> separate thread about that)
> >>
> >>    ...ant
> >>
>
> What/when is 1.0? Good question :) There has been a lot of progress in
> the recent 0.90 and 0.91 releases and I agree that Tuscany SCA is
> getting close to a 1.0 release.
>
> So, let's start discussing "What is Tuscany 1.0". I'm moving this thread
> to the tuscany-user list as I'd like to get feedback, requests and ideas
> from Tuscany users.
>
> Speaking for myself, here's some thoughts on what I'm interested in
> having in a 1.0 release:
>
> * SCA assembly spec 1.0 support
> Looks close to complete here, I think it just needs a little more
> testing and a simple implementation of a distributed domain. Simon seems
> to be making good progress in that area. Also I'd like to have a simple
> admin console to add/remove contributions and composites and allocate
> components to nodes.
>
> * SCA Policy framework 1.0
> Modules policy and policy-xml are taking shape. Having one concrete
> policy like Security implemented on top the framework would be good.
> Maybe Venkat could give his thoughts on this?
>
> * Extension points for component implementations, bindings, databindings
> and policies
> SPIs need a little cleanup as they're starting to carry a number of
> deprecated interfaces/methods. There's no extensibility mechanism for
> policies yet but it shouldn't be too hard to add that with a pattern
> similar to the existing extension points.
>
> * SCA Java APIs and Annotations 1.0
> Almost complete, just missing a complete implementation of
> ServiceReferences and a few conversational annotations. I'd like to
> refine the SCADomain.getService() API too. Also, on a separate but
> related note, a better Java proxy (better than a JDK proxy) would be
> great, I've seen a Cglib proxy contributed recently, how about extending
> that idea to all proxies?
>
> * Spring component implementation
> This looks in a good shape. Mike, what else are you planning to do there?
>
> * WS binding
> What is left to do? The SCA Java Releases wiki page lists some work
> items in this space, which ones do people think should be done for a 1.0
> release?
>
> * JMS binding
> Seems to partly work but will need a little more to align with the
> latest spec. Anybody interested in helping with it?
>
> * Feed and JSON bindings
> IMO important to have to integrate with Web 2.0 apps. The Feed binding
> is fine as far as I can tell. What do people think remains to be done
> for the JSON binding?
>
> * Scripting component implementation
> I've been a happy user of <implementation.script> but have not tried
> using complex types and much integration with bindings. What's left to
> be done here?
>
> * Geronimo integration
> I'd like to be able to deploy SCA contributions to Geronimo, looks like
> there's good progress on that front. I'd also like to support the
> integration of Webapps in SCA compositions as <implementation.web>
> components.
>
> * Docs
> Our architecture docs could use some improvements and cleanup :). For
> user docs, what do people think about developing more tutorials and
> variations around the Online Store tutorial?
>
> * Samples
> Some of them need minor cleanup. Are we missing samples in any specific
> area?
>
> * Other implementation and binding extensions
> We have starters or partial support for <implementation.notification>,
> <implementation.bpel>, <binding.ejb>, <binding.rmi>,
> <implementation.osgi>. Could people help get these extensions in the
> release?
>
> Thoughts? Anything people would like to discuss and get included in
> Tuscany SCA 1.0, please bring it up...
>
> --
> Jean-Sebastien


The simple admin console to add/remove contributions etc sounds good, i'd
quite like that to work with the webapp distribution - what do people think
about having the webapp distribution? I think its good and makes all the
things like the multiple contribution support make more sense and easier to
use, most other similar projects have a war distribution - axis2, synapse,
servicemix, mule etc, but do we want this?

Not sure supporting every corner of all the SCA spec's is necessary for a
Tuscany 1.0, if we do fine, but i think its more important that Tuscany SCA
just does useful things and is useable, so +1 to things like improving the
diagnostics and error handling story, and to making things more easy to use.
Getting some resolution and consistency on the binding URIs that has being
discussed on other threads would be part of that, as would the SPI and
samples tidy up, and making all the wsdl tooling and databinding things work
well together.

Policy support would be great but isn't so exciting unless we've something
that actually uses it, so i think we should try real hard to get WS-Security
or WS-RM going with the WS binding so we can show SCA really does make it as
easy as "Say requires='confidentiality'. Done.".

There's also lots of little things we should do, cleaning up svn and
artifact names etc, we could review all TODO/FIXME comments in the code,
maybe raise JIRAs for the more significant ones and add jira number to
comment and see what that brings to light.

   ...ant