Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-3997

Jacorb subsystem uses magic socket binding names

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 7.1.0.Final
    • IIOP
    • None

      In JacORBSubsystemAdd:

      CorbaORBService orbService = new CorbaORBService(props);
      final ServiceBuilder<ORB> builder = context.getServiceTarget().addService(
      CorbaORBService.SERVICE_NAME, orbService);
      // inject the socket bindings that specify the JacORB IIOP and IIOP/SSL ports.
      builder.addDependency(SocketBinding.JBOSS_BINDING_NAME.append(JACORB_SOCKET_BINDING), SocketBinding.class,
      orbService.getJacORBSocketBindingInjector());
      builder.addDependency(SocketBinding.JBOSS_BINDING_NAME.append(JACORB_SSL_SOCKET_BINDING), SocketBinding.class,
      orbService.getJacORBSSLSocketBindingInjector());

      The JACORB_SOCKET_BINDING and JACORB_SSL_SOCKET_BINDING values should be coming from some configuration attributes, which perhaps have those constants as their default values. Users can name socket-binding configs whatever they want; the names we provide in our standard configs are just obvious defaults.

              sguilhen Stefan Guilhen
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: