Hi, some comments in line

There has been many commits and good progress the last few days, so I
spent a little bit of time checking the status of the trunk.

Here's a summary of what I found:
- The code cleanup is almost complete, I think there's a little bit work
left to refactor one last .spi. package, remove a few dead classes, also
it looks like Raymond has started to clean up the Scope registry and
WorkContext I'm not sure if it's finished or not.
- The Java, Script and RMI extensions are now stable, as well as the
sample implementation, binding, and data binding extensions.
- It looks like we have a reasonable Web app story with a servlet
context listener, but it may require a little bit of cleanup to avoid
confusion with sca-contribution.xml. I'm also not sure if it allows to
expose Web Services from a Web app, or if we even want to do that now.

Main todo's that I could think of:
- Port the Web Service binding extension to the latest code, as it's
really important to have, and is also used by many integration tests.


I remember seeing a mail from the other Simon saying that he has been
working on this

- Run RAT and check licenses and notices.
- Check why the itest/spec-api test cases are failing.


We also need to  go thorugh the itests that depend on the ws binding once
the ws binding is up

- Create a JAR containing the source of our runtime, to help debugging
in an IDE.
- Are the samples build.xml finished?


Nope - am doing build.xml and READMEs now for samples.

- I have ported the Spring extension to the latest code but need to do a
little bit of cleanup tomorrow before committing it.
- I'm not sure about the JSONRPC binding, wouldn't it be nice to have it
too?
- Lazy loading of our modules to avoid loading too many dependencies
when using tuscany-sca-all.jar.
- Rename the packages to *.sca.* but I would suggest to delay this to a
later point some time next week after our first RC.

And there's probably a few more :)

--
Jean-Sebastien


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to