Create generic SA invoker [INT-855]

[spring-operator]

Oleg Zhurakousky opened INT-855 and commented

When interface also contains implementation we need a generic component and configuration to invoke such implementation.
This way interface could be exposed as Gateway allowing a message to be passed through the SI hoops (e.g., re-prioritized, filtered etc...) until it is ready to be passed to the actual implementation such as SA.

---

No further details from INT-855

[spring-operator]

Mark Fisher commented

I think what your describing is the auto-generation of a Gateway proxy using an interface that exists on the "ref"-ed bean of a downstream service-activator? I'm moving this to M4 so we can discuss it a bit more.

[spring-operator]

Oleg Zhurakousky commented

I think you're right. That is exactly what I want.

[spring-operator]

Oleg Zhurakousky commented

This issue was opened with OSGi services in mind where OSGi service could be exposed via interface but actually backed by an implementation which creates a bit of miss-connection when OSGi service is represented by SI Gateway, but needs to eventually delegate to the actual implementation.
However there is a natural SI way of handling this via exporting Gateway as an OSGi service and delegating the flow to Service Activator backed by an actual implementation, so essentially it is not really needed.