TODOs / Tasks for Milestone 2 (M2)

The next release of Tuscany Java SCA - Milestone-2 (M2) is tentatively planned for October. The following is target content for M2 and its status.

Guidelines

Here are some points to help in updating information on the Release Items.

Every release item has four aspects(currently) and a status associated with each aspect. The status includes the list of things 1) that are complete 2) things that are remaining and are necessary to be completed before the feature is included in the release. Categories are:

Feature / Functionality Aspect ii. Working samples

- This includes the list of working samples. - This item may be sharing a sample with other features. For example Component Properties does not have a sample of its own, but the container samples demonstrate them.

iii. Documentation Aspect

- This deals with any documentation that is to be in place to explain the feature / functionality. Enough for the users to pick up and work with it. - If documentation related to the item in question is not substantial to stand on its own, then mention if the related documentation is going to be a part of a bigger one elsewhere. For example there is no specific documentation planned for RMI Bindings. The specific of this shall be added to a more general documentation on Tuscany Binding Extensions.

iv. Blocking JIRAs

Are there known critical JIRA issues that are blocking this feature from being released?

List of functions is created from mailing list. Please help complete the list if anything is missing.

Please cut/paste this template if you are adding a new item.

1. <Feature Name> - in/out? TBD (Owner : <?>)

* Feature / Functionality

Completed:

Remaining:

* Working samples

Completed:

Remaining:

* Documentation

Completed:

Remaining:

* Blocking JIRAs?

<list the JIRA nos.>

Release Items (status)

Here are the list of Release Items and Sub-items within each.

Host distributions

1. Standalone - in/out? TBD (Owner : Meeraj / Jeremy)

* Feature / Functionality

Completed:

Boostrapping the Tuscany Runtime (loading system and application SCDLs)

Remaining:

Locating and Loading Extension Dependencies (please move this up if complete)

Client side - 'Local' (in same process) client with callback works across composites

Server side - 'Local' (in same process) server with callback works across composites

Over webservices:

- The async client with callback works with async ws over http two-way connection based on some assumptions which requires the spec to well define the interaction patterns. - The async ws with callback works over http two-way connection based on similar assumptions as async client.

Samples

Currently Big Bank is working for the most part. The real stockquote function is not there, but I don't consider this a stop release issue. It also uses it's own SCDL for extensions because of Jira TUSCANY-765. In my opinion none of these are a stop ship issue or a reason to not have Big Bank for M2.

Java Component Implementations for calculator funtions and exposing them as Web Services

* Documentation

Completed

Document explaining the setup and running of the sample

Old Status - ignore for now

sync is working, async in progress -

* Working Status

* Working Status

Ant Elder : For the Axis2 Web service binding

support 0.96 spec

move to AXIS2 1.1 (if they get the release out soon)

Jeremy : We can't release with the current SNAPSHOT dependency (as SNAPSHOTs are not reproducible). I hope they get this done in time (progress looks good with AXIOM and XmlSchema being released) but if it looks like it will slip we need to decide whether to hold our release or to cut our own known-revision version (not really a good option).

interop testing

sort out WSDL usage with registry/interface.wsdl/binding.ws

binding.celtix:

Q: where are we?

binding.rmi:

Q: is this working? complete?

Venkat : Yes, this is working. Will include some more testcases to improve coverage.

Updates

(Venkat - Oct 8th) : Have included a few more testcases (with Ant's help) and a helloworld sample to demonstrate RMI services and reference over Tuscany Java SCA standalone.

databinding.axiom: assuming this is complete

Raymond Feng : Yes, as a staging statement, we can transform OMElement to XMLStreamReader and vice versa. Other databindings such as SDO, JAXB or XMLBeans have been supported by multi-hop transformations.

Optional extensions

binding.jsonrpc -

Q: in or out?

Luciano Resende : I was planning to take a look at that, but working on BigBank first...no big feelings about going in or out...

Bert Lamb : For what it is worth I am getting started looking more at the jsonrpc binding and attempting to make it more Dojo friendly and hopefully being able to make it support references. So I guess the question is, do we want to pull it into the M2 release if I may be making potentially significant changes to it.

binding.osgi -

Q: in or out?

databinding.xmlbeans -

Q: in or out?

databinding.castor -

Q: in or out?

Raymond Feng : Several transformers have been implemented, we need some more testing and integration efforts here.

container.groovy -

Q: in or out?

any other bindings or containers to be in?

Venkat : Will need Ant's perspective on including 'Ruby'. A functional version of

it is already available in the SVN repository.

Host distributions

Standalone -

Q: which extensions should be in?

Web -

Q: do we still need this now we have the war plugin?

WAR Plugin -

Q: do we need web.xml editing?

Sample applications

samples(in progress)

Q: do we have the right ones? are there any we don't need? what is the form for these in the release - bundled as source, separate bundle?

Ant Elder : There's also work that needs to be done for the all the samples and distribution stuff that i'd like to help with once we work out what they should look like.

sca/services/bindings/binding.rmi/src/samples (complete)

Standalone sample for RMI Service and RMI Reference complete.

Other areas

SDO distribution - are we ready? where are we with samples, doco, legal review?

A release candidate RC1a is available on http://people.apache.org/~kelvingoodson/sdo_java/RC1a/ It is not yet ready for final release. It has an EMF snapshot dependency currently (2.2.1 should be ready before end of September). I haven't worked out how to get the project status document in place in the distro files yet. There are a number of other small issues. I'm cutting a branch and will cut a tag when all issues are resolved.

DAS distribution -

Q: are we ready? where are we with samples, doco, legal review?

Luciano Resende : Had couples fixes that went in last week : Tuscany-441 / Tuscany-725 After legal review, found couple issues and waiting for someone to commit TUSCANY-726. After that should be done...

SCA distribution - doco? legal?

Release Documentation

Yang ZHONG : I can help with the Release Documentation.

Website - are we generally happy with the site? is anyone planning on working to update the site for M2 content?

Venkat : Will look up the website and check for things to be done and the help in getting that up.

Specs

Targeted Features

SNAPSHOTs have been posted to the Apache repo.

Q: are there any changes to SDO pending? Are we happy with the version there?

Frank Budinsky : The SDO api changes were committed in revision 442403. I think that may be after the snapshot was taken. On the dependencies issue, we need to upgrade EMF to the 2.2.1 release version. I believe that it's going to be published this week.