Possible SCA, Mule Integration Points

Integrate with an existing SCA implementation

SCA deployment integrates Mule services

#1 SCA MULE (ESB) Binding

A binding would be implement to define a specific access mechanism to to invoke SCA services for MULE (ESB)
Why create a binding for MULE(ESB)?, How would it differ to jms/ws/file/http? Why not just use an existing SCA binding/Mule transport for this?

#2 SCA MULE(ESB) Component Implementation Type

Mule would be implemented as a SCA Implementation type alongside Java/Spring/BPEL/PHP/C++ etc.
Doesn't conceptually make a lot of sense because i) an ESB is more for integration than component implementation, ii) If there is a need to integration Mule services with SCA services this would probably be best done via services/references and endpoints.

#3 Mule Transport SCA Adaptors/Wrappers

Mule Transport Adaptors/Wrappers to allow them to be used as SCA bindings

#4 Other SCA Integration Styles

Mule deployment integrates SCA services

#5 Use SCA Composites/Components via Mule Container Context

Minor addition to Mule.
Currently we would only beable to support SCA components/composites with Java Interface types

#6 Use SCA Composites/Components via a Mule "SCA Component" implementation.

Minor addition to Mule.
By using a customer component implmentation rather than a container context there are more things we can do, so it is possible we would be able to support other interface types etc.

#7 Use SCA Composites/Components via mule endpoints, SCA bindings

SCA Composites/Components would be invoked from mule via mule endpoints/sca bindings
Nothing to implement.

Implement "support" for SCA.

#8 Mule Implement SCA Assembly Model

The most ambitious option.
Will require some additions/changes to mule core to enable this (e.g. interfaces, ability to more declaratively wire endpoints together, ability to compose service hierachically.)
SCA would be optionally. An SCA configuration could be used to configure mule instead of mule config file.
Existing binding and implmentation type specifications would need to be supported if we want to fully support SCA otherwise it would just be SCA config with limited or Mule specific implementation types and bindings.

Hybridize Mule & SCA Models

The analogy you may wish to consider is that you need a high speed ice-cream van because you've spotted a gap in the market.

Phase 1. Get a high speed normal van, get an ice-cream van. Tow the ice-cream van with it. Technically you have solved the problem of your high speed ice-cream van. Just.
Phase 2. Cut the van in half, cut the front of the ice-cream van, weld them together and re-spray the whole truck. Much better, but not exactly purpose built.
Phase 3. Design a high speed ice-cream ban based on experiences with Phase 2 based on parts from both vans and the odd custom bits needed.

The hybrid would be phase 3.