On 10/17/07, Raymond Feng <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Thank you for participating the discussion. I collected all the input we
> have so far at the following WIKI page:
>
> http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Roadmap+Discussion
>
> Please feel free to add/update to make it an ongoing community effect.
>
> Hopefully we can start to turn them into actions and I believe some
> specific
> discussions have been carried on the ML. As always, your contributions are
> welcome.
>
> Thanks,
> Raymond
>
> ----- Original Message -----
> From: "wang feng" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, October 16, 2007 7:18 PM
> Subject: Re: Re: [DISCUSS] Tuscany SCA Roadmap and next releases
>
>
> > Hi all,
> >
> > We have used Tuscany 1.0 in our product and found some features is
> > important to us.
> >
> > - Support hot deployable on contribution and composite.
> > This should be have a recursive algorithm to update the correlated
> > component when it has been referenced.
> >
> > - Support SDO namespace when using websservice.
> > Deploy a service to webservice,a schema file used in SDO and have sdo
> > namespace such as commonj.sdo/java or commonj.sdo/xml,we should support
> > the feature when parsing the wsdl.
> >
> > - Support load contribution as a osgi bundle.
> >
> >
> > Thanks,
> > wangfeng
> >
> >
> > On 2007-10-17, Simon Laws <[EMAIL PROTECTED]> wrote:
> >
> >>On 10/16/07, Luciano Resende <[EMAIL PROTECTED]> wrote:
> >>>
> >>> For implementation.bpel, we need to finalize support for references,
> >>> and we might want to do introspection of the BPEL process.
> >>>
> >>> On 10/16/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
> >>> > [snip]
> >>> > ant elder wrote:
> >>> > >
> >>> > > - Fix nightly builds (looks like this may be going again now)
> >>> > >
> >>> >
> >>> > Yes it is.
> >>> >
> >>> >
> >>>
> http://vmbuild1.apache.org/continuum/buildResults.action?projectGroupId=19&projectId=277
> >>> >
> >>> > [snip]
> >>> > > - Fix all the build issues (maven 2.0.6/2.0.7/JDK6/empty
> repository)
> >>> so new
> >>> > > users building Tuscany have a good experience
> >>> > >
> >>> >
> >>> > After the changes I made last week I think this is now all fixed
> >>> > (except
> >>> > for JIRAs TUSCANY-1846 and TUSCANY-1847). I am currently building
> with
> >>> > Maven 2.0.7 and both JDK5 and JDK6.
> >>> >
> >>> > Could people please try other Maven combinations? 2.0.5, 2.0.6, and
> >>> > report any errors? Thanks.
> >>> >
> >>> > [snip]
> >>> > > - Get binding.jms and implementation.bpel more spec complete.
> >>> > > - For JMS maybe have a host-jms module so you don't have to start
> a
> >>> separate
> >>> > > JMS server or can use the the Geronimo one if thats where Tuscany
> is
> >>> running
> >>> > >
> >>> >
> >>> > What's missing in binding.jms and implementation.bpel? Could people
> >>> > working on these modules give a quick overview?
> >>> >
> >>> > --
> >>> > Jean-Sebastien
> >>> >
> >>> >
> >>> >
> ---------------------------------------------------------------------
> >>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>> > For additional commands, e-mail: [EMAIL PROTECTED]
> >>> >
> >>> >
> >>>
> >>>
> >>> --
> >>> Luciano Resende
> >>> Apache Tuscany Committer
> >>> http://people.apache.org/~lresende
> >>> http://lresende.blogspot.com/
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>> For additional commands, e-mail: [EMAIL PROTECTED]
> >>>
> >>> For binding.jms the user guide shows you that most of the options
> still
> >>need to be implemented.
> >>
> >>http://incubator.apache.org/tuscany/sca-java-bindingjms.html
> >>
> >>There are a few people either working on this or have expressed an
> >>interest
> >>in working on it. There is quite a lot on incremental stuff that can be
> >>done
> >>for anyone else who is interested.
> >>
> >>Regards
> >>
> >>Simon
> >>
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> Thanks for collating all these points Raymond. I also have a laundry list
of things I would like to see which I will add to the wiki page.
We have been through this process in the past and we have started with a
long list, stripped it down to what can be addressed for the next release.
The work is done, the release is made and we start a new list.
As Sebastien suggested in the mail that started this I would like to see
this list have scope greater than the next release.
I would also like to maintain things that don't fit in the list for some
reason or another rather than just discarding them
How about everything becomes a JIRA enhancement and the Roadmap
exercise is about organizing/prioritizing/finding people interested in those
JIRA.
I would like to encourage people to continue to extend the list even once we
have started toward the next release.
To me the term "Roadmap" suggests something relatively firm and potentially
quite high level. I've been asked by people what small projects they could
start on with Tuscany. It would be good to capture and maintain all of the
thoughts for enhancement people have so that answering that question is very
easy.
Regards
Simon
