Scenario: Using the container on just one endpoint

» Home » MicroKernel/Windsor » Documentation » Facilities » Remoting Facility » Scenario: Using the container on just one endpoint

KernelInOneEndPoint.Sample.zip (9.83k)

Depending on the situation you might want (or dont have other option) to use the container on just one endpoint. In this case the facility is restricted to only configure the remoting infrastructure (if on server side) and to configure and provide the activators (if on client side)

This usage is not useless, in fact it's a good option if you plan to use an IoC container as the application rendesvouz. Just be aware the if you're using the container on the server endpoint, the components published, when requested by the client endpoint, will be server directly by .net remoting. Castle will not be able to intercept it. This might be undesired if, for example, you're using the NHibernate facility to provide automatic session creation and disposal, or the Automatic Transaction facility to manage transactions. Even auto wire is not going to work.

If this is your situation, check the last scenario.

The following snippets exemplifies this usage.

Client Container Configuration
Server Container Configuration

No configuration


<castle>

    <facilities>
        <facility 
            id="remote.facility" 
            type="Castle.Facilities.Remoting.RemotingFacility, Castle.MicroKernel"
            remotingConfigurationFile="RemotingTcpConfig.config">
        </facility>    
    </facilities>
    
    <components>
        <component 
            id="remote.console.component" 
            service="Example.Shared.IRemoteConsole, Example.Shared"
            type="ServerApp.RemoteConsoleImpl, ServerApp"
            remoteserver="singleton" uri="remoteconsolecomponent" />
    </components>

</castle>

Home

Castle Stronghold

Scenario: Using the container on just one endpoint