How are we going to handle the Tuscany extensions ? Are we going to include all the implementation.xxx and binding.xxx from Tuscany or only the minimum required to support the SCA spec 1.0 SCDL elements ?
If what we want is the SCDL Model, we might be able to create a Contribution Bootstraper, and avoid extra dependencies from ReallySmallRuntime... in the past, I had something like that for the Contribution iTests, where the contribution service was being created isolated of the Runtime to parse a contribution and create a Model ... On 10/10/07, ant elder <[EMAIL PROTECTED]> wrote: > On 10/10/07, Simon Laws <[EMAIL PROTECTED]> wrote: > > > > On 10/10/07, ant elder <[EMAIL PROTECTED]> wrote: > > > > > > How about making a tuscany-scdl4j jar for this? Something like the > > > tuscany-sca-all jar but only containing the modules and classes > > necessary > > > for processing the scdl and creating model objects? We did talk about > > > having > > > something like this at one point, is it worth revisiting? > > > > > > ...ant > > > > > > On 10/9/07, Sean Zhou (JIRA) <[email protected]> wrote: > > > > > > > > Bootstrapping a subset of Tuscany runtime to support object modeling > > in > > > > tools > > > > > > > > > > > > > ----------------------------------------------------------------------------- > > > > > > > > Key: TUSCANY-1840 > > > > URL: > > https://issues.apache.org/jira/browse/TUSCANY-1840 > > > > Project: Tuscany > > > > Issue Type: New Feature > > > > Components: Java SCA Core Runtime > > > > Affects Versions: Java-SCA-1.0.1 > > > > Environment: Windows or Linux > > > > Reporter: Sean Zhou > > > > Priority: Critical > > > > Fix For: Java-SCA-1.0.1 > > > > > > > > > > > > When adopting Tuscany object models in a tooling environment, a subset > > > of > > > > Tuscany runtime requires bootstrap such as creating extension points > > and > > > > factories. Currently there are no standard API methods or classes for > > > > Tuscany bootstrapping for modeling. > > > > > > > > -- > > > > This message is automatically generated by JIRA. > > > > - > > > > You can reply to this email to add a comment to the issue online. > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > I think it would. Also it would be useful to take a look at what the > > minimum > > set of steps (from the ReallySmallRuntime) are required to get a > > contribution loaded into the assembly model. Currently we all use > > ReallySmallRuntime but it's doing a number of things that are not required > > to get just the assembly model up. > > > > Simon > > > > Right i agree, and I guess initially the scdl4j jar could include copies of > whatever code from ReallySmallRuntime is necessary to load a contribution > and then later on maybe simplify all the runtime code so it just depends on > the scdl4j code. > > ...ant > -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
