On Aug 16, 2006, at 2:49 PM, Jim Marino wrote:
3) Baseline extensions - ones we think are essential for users
idl.wsdl
binding.axis
binding.celtix
binding.rmi
databinding.axiom
databinding.sdo
databinding.jaxb
container.javascript
container.spring
I'm not sure what the difference is between baseline and optional.
I think all extensions are optional unless one is being used and
has dependencies. If the distinction is to deal with voting issues,
maybe we could group things together as long as there is a way to
not have them physically bundled together. Can you explain the
linkage between 3,4,5 as I think there may be a terminology issue?
From a technical perspective, yes, all are optional relative to the
core and yes there may be dependencies between them.
The grouping here is "stuff that we think is useful to a user and
want to ship as a bundle" and would be input to the host distros in
5). We would want these to be in sync and tested together.
4) Optional extensions - nice to have but which may not be ready
to bundle
binding.jsonrpc
binding.osgi
databinding.xmlbeans
databinding.castor
container.groovy
5) Host distributions - host environments that each form the basis
for each bundle
Standalone (with axis, celtix, rmi, spring)
Web-app (with axis, celtix, rmi, json, spring, javascript)
These would be the things we would expect users to download to start
using Tuscany. These would be targeted at providing the extensions
users would need to do something useful. I was thinking Standalone
would be a command line client environment, Web-app would be what you
would want to use in a war (the J2EE variety).
Perhaps we should add another:
Minimal - distro of just the core and its dependencies to
which users could add extensions
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
