Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.
The following page has been changed by JeanSebastienDelfino: http://wiki.apache.org/ws/Tuscany/Roadmap ------------------------------------------------------------------------------ == Subsystem assembly model == * support for subsystem SCDL - * ModuleComponents only no externalService and entryPoint at the subsystem level + * moduleComponents only no externalService and entryPoint at the subsystem level - * Support for wiring/specifying endpoints on externalServices + * support for wiring/specifying endpoints on externalServices - * Support for overriding properties of moduleComponents + * support for overriding properties of moduleComponents - * On Tomcat, subsystem maps to a Tomcat instance, moduleComponent maps to a Web app + * on Tomcat, subsystem maps to a Tomcat instance, moduleComponent maps to a Web app - * In J2SE, you can run a single moduleComponent + * in J2SE, you can run a single moduleComponent == Client and implementation model == * align implementation with a subset of SCA 0.9 @@ -31, +31 @@ * no service references * no conversational, no callbacks + == Runtime architecture improvements == + * remove Tuscany``Module``Component``Context``Impl, transition to new context architecture and make sure model, loaders, builders, config and context are decoupled + * Fix how proxying and invocation chains works, distinguish source and target proxies / invocation chains + == Development Tools == - * WSDL2Java and Java2WSDL generators + * WSDL2``Java and Java2WSDL generators * XSD2SDO and Java2SDO generators * both in the form of API and maven plugins == Bindings == - * Web Service binding using AXIS 2 (SOAP/HTTP, doc literal only, support for streaming) + * web Service binding using AXIS 2 (SOAP/HTTP, doc literal only, support for streaming) - * Pluggable data-binding (start with regular Java objects and SDO) + * pluggable data-binding (start with regular Java objects and SDO) * I think that we can live with just a WS binding for now and look at the default SCA binding later (maybe it'll just be a variation of the WS binding with some defaults anyway). + * JMS binding + + == Data Access Service == + * complete the transition to SDO2 + * DAS integrated into Big``Bank sample + * best-practice DAS sample (stand-alone and SCA-integrated) + * datasource definition in config file + * tools support - export metadata - return the SDO Types and/or write an XML file that contains the types created from the config + resultSetMetadata == Extensibility == - * Support contribution of a new binding (I'm thinking about a sample HTTP binding to illustrate that) + * support contribution of a new binding (I'm thinking about a sample HTTP binding to illustrate that) - * Support contribution of a new component type (Ant's sample Javascript component type) + * support contribution of a new component type (Ant's sample Javascript component type) == Admin == * just doc or basic tools (maven plugin?) to install/uninstall a subsystem and module component * just doc or basic tools to start/stop a subsystem and module component * wiring, configuration of module component properties require editing SCDL file and bouncing the subsystem - * Simple monitoring/logging + * simple monitoring/logging == Target environments == * JDK 5.0
