As we're still in the milestone phase we're still in the business of making changes to SPIs/APIs although I expect they're starting to settle down a bit. It would be useful to get into the habit of tracking changes in SPI so that as we get closer to the full release we can tell how stable we are.
Firstly, is the list of APIs/SPIs included on the 2.x docs page [1] accurate? There seems to be a lot of package names in this list. I'm interested in the core things that A - extension writers should extend when build new binding, implementation, policy etc, for example, the base Binding model class B - extension writers should call in order to interact with the runtime, for example, the extension point registry Currently the list seems to have listed just about all the non-implementation packages in the project. The majority of these are extension specific which I think looks very confusing for someone trying to work out what the SPI actually is. Is there a good reason all these are listed? Regards Simon [1] http://tuscany.apache.org/documentation-2x/tuscany-2x-extensibility-and-spis.html -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
