Ok I've added a TargetInvokerExtension. The clone method doesn't seem perfect yet as subclasses now aren't forced to implement clone by the compiler.
...ant On 8/10/06, Jim Marino <[EMAIL PROTECTED]> wrote:
Yea we could do that. Probably the one invoke method that takes the payload from the message could be abstracted and if there is a special target type that needs access to message headers or something it could just override it. Do you want to create one as I'm out later today? Jim On Aug 10, 2006, at 5:35 AM, ant elder wrote: > Great stuff Jim, these changes look really good to me. Makes > implementing a > binding way easier. > > What do you think about having an abstract SPI class for the > TargetInvoker > which includes all the cachable, optimizable and invoke methods? > > ...ant > > On 8/10/06, Jim Marino <[EMAIL PROTECTED]> wrote: >> >> I've checked in an example of a simple binding (r430211) that >> demonstrates creating services and references. For references, the >> binding just echoes a single param back to the client. >> >> Related to this, I've also completed a series of commits that move >> application wiring from the responsibility of the builders to >> initiate up into the builder registry which delegates to the system >> wire service. Once a Service, Reference, or Component is created and >> returned from a builder, the builder registry will invoke the wire >> service to create the appropriate inbound and outbound wires. These >> wires will then be injected into the Service, Reference or Component. >> At a later point, the connector will bridge outbound (source) to >> inbound (target) wires. >> >> Services and References will generally not need to do anything other >> than hold onto the wires (implemented as a convenience by the >> extension base classes), but components are responsible for >> implementing a strategy for injecting them onto implementation >> instances as the latter are requested. In the case of Java, this >> involves delegating back to the wire service to create a proxy >> fronting the wire and implementing the appropriate reference >> interface. This proxy will be injected onto an implementation >> instance as it is created. BPEL or an other implementation type may >> do something entirely different and maybe not even use proxies. >> >> Certain types of composite components may need to manually bridge >> Services to targets. For example, a Spring composite is opaque to the >> SCA wiring fabric in that its beans are not visible as components. >> The Spring builder is responsible for delegating to the builder >> registry to create a service which it then must provide with a target >> invoker capable of dispatching into the Spring application context >> and to a target bean. This can be viewed as the SCA wiring mechanism >> delegating to Spring for internal wiring. >> >> Jim >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
