Swordfish Documentation: Architecture: Internal Service Proxy

Component diagrams

Sketch of сomponent сlasses for Internal Service Proxy Plugin

Plugin description

Example of InternalProxy usage:

• proxy injection (at runtime available as OSGi service):

    <osgi:reference id="internalProxy"
    	interface="org.eclipse.swordfish.core.proxy.InternalProxy" />

    <bean id="ASFRegistryProvider"
        class="org.eclipse.swordfish.internal.resolver.backend.remote.ASFRegistryProvider"
        p:proxy-ref="internalProxy"/>

• invocation of target service:

public class ASFRegistryProvider extends AbstractDocumentProvider {

    private InternalProxy proxy;

    @Override
    public Collection<ServiceDescription<?>> getServiceProviderDescriptions(QName interfaceName) {
        String res = null;
        try {
            res = proxy.invokeRequestResponseOperation(
                QName.valueOf("{http://services.sopware.org/registry/ServiceRegistryProvider/1.0}ServiceRegistryProvider"),
                QName.valueOf("{http://services.sopware.org/registry/ServiceRegistryProvider/1.0}xlookUp_serviceProvider"),
                "<inMessage/>");
        } catch (Exception e) {
            e.printStackTrace();
        }

        // further processing...

        return null;
    }

    public void setProxy(InternalProxy proxy) {
        this.proxy = proxy;
    }

}

During invocation InternalProxy performs the following steps:

• creates new NMR Exchange for provided operation;
• lookups outbound endpoint from the NMR using provided service name;
• sends exchange to NMR according to selected message exchange pattern (e.g. "http://www.w3.org/ns/wsdl/in-out").

NOTE: Current version of proxy assumes that outbound endpoint of target service is already registered within ServiceMix NMR.