Minimum Bring Up
Modules | Diff | Why? | Merging Status |
tuscany-assembly-1.4-EQUINOX-SNAPSHOT.jar |
| Builders used to be implementation classes. Now we use the extension registry to get builders by interfaces. |
|
tuscany-assembly-xml-1.4-EQUINOX-SNAPSHOT.jar |
| It's extended to support JDK service provider patttern based factories such as XPathFactory, XMLInputFactory in addition to the model factories. Rename the interface to refactor the new function. |
|
tuscany-assembly-xsd-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-binding-sca-1.4-EQUINOX-SNAPSHOT.jar |
| provider package contains the classes that implement the Provider SPIs. This package should NOT be exported. |
|
tuscany-binding-sca-xml-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-contribution-1.4-EQUINOX-SNAPSHOT.jar |
| The changes are to fix the contribution processing (we used to read and resolve contributions one by one). There is no need to have a ContributionService. We now just use the PackageProcessor, StAXArtifactProcessor to parse the package and load artifact models. |
|
tuscany-contribution-namespace-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-contribution-java-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-contribution-xml-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-core-1.4-EQUINOX-SNAPSHOT.jar |
| Event and Store are dead code. |
|
tuscany-core-databinding-1.4-EQUINOX-SNAPSHOT.jar |
| The databinding aliases are removed from trunk and should be merged into sca-equinox |
|
tuscany-core-spi-1.4-EQUINOX-SNAPSHOT.jar |
| ServiceDiscovery changes to make it work with OSGi |
|
tuscany-databinding-1.4-EQUINOX-SNAPSHOT.jar |
| The databinding aliases are removed from trunk and should be merged into sca-equinox |
|
tuscany-databinding-jaxb-1.4-EQUINOX-SNAPSHOT.jar |
| The databinding aliases are removed from trunk and should be merged into sca-equinox |
|
tuscany-definitions-1.4-EQUINOX-SNAPSHOT.jar |
| Remove SCA prefix |
|
tuscany-definitions-xml-1.4-EQUINOX-SNAPSHOT.jar |
| Remove SCA prefix |
|
tuscany-endpoint-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-extensibility-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-extensibility-equinox-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-host-http-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-implementation-java-1.4-EQUINOX-SNAPSHOT.jar |
| Refactor implementation-java to avoid having the SPI interfaces reference implementation classes as it doesn't work with OSGi imports/exports. |
|
tuscany-implementation-java-runtime-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-implementation-java-xml-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-implementation-node-1.4-EQUINOX-SNAPSHOT.jar |
| See the assembly module |
|
tuscany-implementation-node-runtime-1.4-EQUINOX-SNAPSHOT.jar |
| Remove SCA prefix |
|
tuscany-interface-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-interface-java-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-interface-java-xml-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-interface-java-jaxws-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-monitor-1.4-EQUINOX-SNAPSHOT.jar |
| Use the factory pattern to create Monitor instances |
|
tuscany-node-api-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-node-launcher-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-node-launcher-equinox-1.4-EQUINOX-SNAPSHOT.jar |
| Bootstrap the Equinox runtime from classpath or distribution and run the SCA node apis |
|
tuscany-node-impl-1.4-EQUINOX-SNAPSHOT.jar |
| Simplify the node implementation by using the Workspace to load and resolve contribution dependencies. Remove all the code to discover contributions using various methods. Now we have the ContributionLocationHelper in the node api to help find the root of the contributions. |
|
tuscany-policy-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-policy-xml-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-sca-api-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-workspace-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-workspace-impl-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-workspace-xml-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
tuscany-xsd-1.4-EQUINOX-SNAPSHOT.jar |
|
|
|
Distribution |
| We now have the capability to produce distributions based on the collection of functions. The distribution structure is slightly changed to be compatible with OSGi, for example, a non-OSGi 3rd party jar now is packaged under its own folder which also contains the META-INF/MANIFEST.MF to form a folder-based OSGi bundle and leave the jar as-is. |
|
Etc |
| Should keep the one in trunk. It only contains a set of templates for developers, not code related |
|
itest |
| We removed the usage of SCADomain to be in favor of SCA Node APIs |
|
samples |
| We removed the usage of SCADomain to be in favor of SCA Node APIs |
|
tools |
| The eclipse plugins are now organized by functional features so that they can installed based on the needs.
|
|
tutorial |
|
|
|
...
Features of OSGi Enablement http://cwiki.apache.org/confluence/display/TUSCANYWIKI/OSGi+Enablement+for+Tuscany+Runtime
Overview of how Tuscany fits in with OSGi http://cwiki.apache.org/confluence/display/TUSCANY/OSGi+Aware+Programming+in+Tuscany
Devloping with Tuscany (with some points on how to bring a module into Eclipse PDE if you want to) http://tuscany.apache.org/sca-java-development-guide-osgi.html
Thoughts on how to get the branch changes merged into trunk http://cwiki.apache.org/confluence/display/TUSCANYWIKI/OASIS+Development+Stream
Presentation about hooking into Equinox http://www.eclipsecon.org/2008/sub/attachments/Equinox_Framework_How_to_get_Hooked.pdf
Older Links
http://wiki.apache.org/confluence/display/TUSCANYWIKI/OSGi+Integration