A corba service can be localized using some different mechanisms: NameService, IOR, corbaname and corbaloc.
The JBI4CORBA component supports all of these methods when it is configured as a provider.
In this configuration the component is a client corba and it looks for the associated servant during the startup of the ServiceUnit, so the user must specify a way to localize the service using a property called localizationType.
The localizationType property can assume the following values: NameService, IOR, corbaname and corbaloc.
The name changes with the localizationType:
| localizationType | name | |
|---|---|---|
| NameService | ||
| IOR | The absolute path where there is a file that contains a IOR | |
| corbaname | The corbaname url of the service | |
| corbaloc | The corbaloc url of the service |
In this example the binding component is deployed using the WSDL file and the localizationType is NameService.
<wsdl:binding name="EchoWSDLJBIPortBinding" type="tns:EchoWSDLPortType">
<imolacorba:binding>
<imolacorba:idl>
... the idl file content.
</imolacorba:idl>
</imolacorba:binding>
[...]
</wsdl:binding>
<wsdl:service name="EchoWSDL">
<wsdl:port binding="tns:EchoWSDLJBIPortBinding" name="EchoWSDLJBIPort">
<imolacorba:address name="ServantTestSimpleWsdl" localizationType="NameService">
<imolacorba:orb>
<imolacorba:property name="org.omg.CORBA.ORBInitialPort" value="1050"/>
<imolacorba:property name="org.omg.CORBA.ORBInitialHost" value="localhost"/>
</imolacorba:orb>
</imolacorba:address>
</wsdl:port>
</wsdl:service>
In this example the binding component is deployed using the WSDL file and the localizationType is IOR. (The servant can avoid the registration in the NameService)
[...]
<wsdl:service name="EchoIorWSDL">
<wsdl:port binding="tns:EchoIorWSDLJBIPortBinding" name="EchoIorWSDLJBIPort">
<imolacorba:address localizationType="IOR" name="c:/wolv/EchoIorWsdlImpl.txt" />
</wsdl:port>
</wsdl:service>