[snip]
ant elder wrote:
Here's todays weekly IRC chat log. The only topic discussed was the
SCA 0.90release, the current plan is to cut a
0.90 release branch this Wednesday.
We went through the open JIRA's targeted at 0.90 to see if anyone wanted
particular JIRA's as must fix for 0.90 and which ones could be
defered. The
current JIRA's for 0.90 are:
http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310210&fixfor=12312478
. Tomorrow I'm going to move all of those out of 0.90 except for
TUSCANY-1247, TUSCANY-1248, and TUSCANY-1265. If anyone has any others
which should be in 0.90 just say.
The samples were also discussed, sounds like most of them are ready,
there's
some issues around the those related to how to write Tuscany extensions,
discussion will continue on the mailing list.
Venkat will run RAT against the current distro's and email the mailing
list
the results, slaws will try the distro's on linux.
The latest distributions built of the trunk code as of just now (r537917)
are at:
http://people.apache.org/~antelder/tuscany/latest/<http://people.apache.org/%7Eantelder/tuscany/latest/>.
Please try these out and report any issues (or even just that you
tried and
a sample worked!)
...ant
Sorry that I missed yesterday's IRC chat. I have a few more things to
add to our TODO list for the release:
I'd like to have in the binary distro a JAR containing the Tuscany
source that people can attach to the Tuscany JAR for debugging in an IDE
(we already discussed this on the list but can't find the thread now).
I am not sure where we are with our Webapp story. If we go with the
context listener approach, we need to adjust it to take its
configuration and list of deployables from sca-contribution.xml instead
of web.xml. If we go with another approach we need to adjust the sample.
For consistency, SCADomain.newInstance() should also work without a list
of composites and take its configuration from sca-contribution.xml if
there is one.
We need some samples to show sca-contribution.xml (adjust some of the
existing samples).
The above items are important IMO as they touch APIs used by application
developers.
One of the goals of this release is stable SPIs. I have reviewed them
and there a few things that I think need to be fixed now to avoid
disrupting changes after the release.
- Package o.a.t.sca.scope is not clean or finalized IMO and since it's
currently only used by the core and implementation-java-runtime modules
I think we should move it to the core module and mature it there, we can
move it back to SPI when it has become a clean SPI.
- Same comment for o.a.t.sca.factory.
- o.a.t.Message has setWire/getWire methods with a FIXME comment
indicating that these methods should be removed, can we remove them now?
- Some of the factories and common runtime services are hardcoded in the
ModuleActivators. The ModuleActivators need a way to get these objects
from the runtime (maybe from the ExtensionPointRegistry) instead of
having to new them up.
I also took a look at the Javadoc for the SPIs and we need to spend some
time fixing it, as some of the Javadoc comments are obsolete or incorrect.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
