On Sat, Nov 22, 2008 at 4:03 AM, Luciano Resende <[EMAIL PROTECTED]>wrote:
> On Fri, Nov 21, 2008 at 11:35 AM, Raymond Feng <[EMAIL PROTECTED]> > wrote: > > Hi, > > > > For stage 1, the distribution could be the core (or the pdetarget). I > would > > really rather stay in the core for JSE and OSGi than rushing to bring up > > other pieces. We are trying to build a better foundation for the 2.x > stream > > now and I don't think we are settled to move into the bringup stage. > > +1 I think that having a better foundation to start will make our life > much easier when bringing up the other pieces of the runtime, > extensions, etc. > > > > > Thanks, > > Raymond > > > > From: ant elder > > Sent: Friday, November 21, 2008 2:29 AM > > To: Simon Laws > > Cc: [email protected] > > Subject: Re: [DISCUSS] Tuscany 2.0 themes? > > > > [[snip]] > > > > I agree there should be some "distribution" items on the stage 1 list. > I'd > > also like to bring up sooner rather than later the various runtime > options - > > so j2se and webapps along with equinox. > > > > ...ant > > > > > > -- > Luciano Resende > Apache Tuscany, Apache PhotArk > http://people.apache.org/~lresende <http://people.apache.org/%7Elresende> > http://lresende.blogspot.com/ > In the gaps today I've been going through the minimum set of 2.x modules using Ramymond's comments [1] to understand changes and making notes about areas that may need more attention before we start pulling in everything else. Here are my raw notes from today so I don't loose them. More later. General ====== Minimum and simplest set of dependendencies use asm (remove cglib) - TUSCANY-2359 still lots of impls being exported get the right things in contrib Get rid of warnings where possible Builder Tidy Endpoint RRB Policy Run with security enabled to see how we stand Look for all TODO/FIXME in the code and review Review JIRA to see what needs to be addressed in 2.x Try and avoid packages appearing in unexpected places. Core package in extensibility for example Test structure How should unit tests operation Sample structure How should samples operate Distribution Runtime options. Let's understand (and document) our minimum runtime useage scenarios, for example, I'd like to know this kind of thing Command line java -jar domain.jar java -jar node.jar Starting node adds it to the domain URL info? java -jar node.jar composite contribution java -jar node.jar configurURL java -jar node.jar debug prod the node from a simple command prompt, force tracing on, etc? Eclipse Right clink on composite file to run Right click on multiple composite files causes them to be stared in the same domain? Webapp Drop web app into container with Generally bundles seem to import their own packages. Why? What is the SPI? Java doc for these minimal modules + Explicit SPI Module Specific Comments ------------------------ [INFO] Apache Tuscany SCA Extensibility ...................... SUCCESS [0.000s] Module Activator - What dictates using this rather than specific extension point Why are there o.a.t.s.core packages here? Change the package or change the module Imports itself and core???? Remove dependency on equinox extensibility. Will have to find a way of having the the equinox module register with the extensibility package. [INFO] Apache Tuscany SCA Policy Model ....................... SUCCESS [3.375s] Needs reorg [INFO] Apache Tuscany SCA Interface Model .................... SUCCESS [1.110s] [INFO] Apache Tuscany SCA Assembly Model XML Schemas ......... SUCCESS [0.015s] All the schema being in one place seems inconsistent [INFO] Apache Tuscany SCA Definitions ........................ SUCCESS [1.094s] Seems OK [INFO] Apache Tuscany SCA Monitor ............................ SUCCESS [0.016s] Seems OK [INFO] Apache Tuscany SCA Assembly Model ..................... SUCCESS [3.250s] Imports itself? Exports Impls. Presumably so that core can extend Separate module for builders, especially now they are an extension point. We do have users who change the builders. [INFO] Apache Tuscany SCA Contribution Model ................. SUCCESS [1.484s] Classloaders? get rid of service package [INFO] Apache Tuscany SCA API ................................ SUCCESS [0.016s] need OASIS versions [INFO] Apache Tuscany SCA Core SPI ........................... SUCCESS [2.297s] How do we understand what constitutes the Tuscany SPI. [INFO] Apache Tuscany SCA Namespace Import/Export Model ...... SUCCESS [1.187s] [INFO] Apache Tuscany SCA Java Import/Export Model ........... SUCCESS [0.031s] [INFO] Apache Tuscany SCA Policy XML Model ................... SUCCESS [0.016s] [INFO] Apache Tuscany SCA Definitions XML Model .............. SUCCESS [1.172s] [INFO] Apache Tuscany SCA XML Assembly Model ................. SUCCESS [3.281s] [INFO] Apache Tuscany SCA Java Interface Model ............... SUCCESS [0.016s] [INFO] Apache Tuscany SCA Core Runtime ....................... SUCCESS [1.187s] Doesn't actually export o.a.t.s.core but extensibility does Move activator into it's own package Wire -> EndpointWire Refine Endpoint vs EndpointReference Runtime component, references and services extend assembly implementations Why not just put them in assembly Invocation seems like a funny set of stuff when the RuntimeWire itself is in assembly Scope needs work. Request scope is going I believe org.apache.tuscany.sca.core.ModuleActivatorExtensionPoint used 3 modules. Shouldn't this be done using normal extension points now DataBindingModuleActivator JavaImplementationModuleActivator JavaRuntimeModulesActivator [INFO] Apache Tuscany SCA Default Binding Model .............. SUCCESS [2.266s] Remote binding decision plug point [INFO] Apache Tuscany SCA Default Binding XML Model .......... SUCCESS [1.328s] [INFO] Apache Tuscany SCA XML Contribution Model ............. SUCCESS [0.016s] Why is the processor.xml stuff here different from that in contribution [INFO] Apache Tuscany SCA XSD Model .......................... SUCCESS [0.093s] [INFO] Apache Tuscany SCA DataBinding Framework .............. SUCCESS [1.141s] [INFO] Apache Tuscany SCA Data Binding for JAXB .............. SUCCESS [1.828s] [INFO] Apache Tuscany SCA Java Interface XML Model ........... SUCCESS [0.031s] [INFO] Apache Tuscany Java Interface for JAXWS ............... SUCCESS [6.688s] [INFO] Apache Tuscany SCA Core/DataBinding Integration ....... SUCCESS [1.125s] [INFO] Apache Tuscany SCA Domain Workspace Model ............. SUCCESS [0.016s] Why is this called domain and not contribution. The workspace is used in the node now as well as in the domain [INFO] Apache Tuscany SCA Domain Workspace XML Model ......... SUCCESS [1.078s] [INFO] Apache Tuscany SCA Domain Workspace Implementation .... SUCCESS [2.265s] [INFO] Apache Tuscany SCA Java Implementation Model .......... SUCCESS [0.032s] [INFO] Apache Tuscany SCA Java Implementation XML Model ...... SUCCESS [1.140s] [INFO] Apache Tuscany SCA Default Endpoint Implementation .... SUCCESS [2.094s] Needs work [INFO] Apache Tuscany SCA Extensibility for Eclipse Equinox .. SUCCESS [5.312s] Has DynamicImport-Package: * [INFO] Apache Tuscany SCA Java Implementation Model .......... SUCCESS [0.047s] [INFO] Apache Tuscany SCA Node Implementation Model .......... SUCCESS [1.282s] I find this confusing so would like to discuss In paricular the runtime part vs just straighforward node modules as control seems to switch backward and forward between the two. I appreciate the desire to have a pluggable node implementation in some sense but having it called implementation doesn't IMO make things clearer. Anyhow a topic for discussion [INFO] Apache Tuscany SCA Node API ........................... SUCCESS [0.000s] [INFO] Apache Tuscany SCA Node Launcher ...................... SUCCESS [0.015s] No suggesting all theseUnderstand the range of start up options, e.g [INFO] Apache Tuscany SCA Node Implementation ................ SUCCESS [5.797s] Policy resolution - currently commented out [INFO] Apache Tuscany SCA Node Implementation Extension ...... SUCCESS [3.500s] [INFO] Apache Tuscany SCA Node Equinox OSGi Launcher ......... SUCCESS [4.609s] [INFO] Apache Tuscany Security Policy Model .................. SUCCESS [0.032s] Needs tidying - think about separation of model and implementation I have puts some of both in here previously Simon [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Equinox+Branch+Merge
