Uploaded image for project: 'Codehaus Cargo'
  1. Codehaus Cargo
  2. CARGO-849

Enhance documententation for cargo.rmi.port and cargo.jboss.naming.port

    Details

      Description

      In the cargo maven plugin you have to set <cargo.rmi.port> in case of not using the default jboss port.
      To know the port I have opened my jboss_home/server/default/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml and look for the rmi port.
      I found this :

      <bean class="org.jboss.services.binding.ServiceBindingMetadata">
      <property name="serviceName">jboss:service=Naming</property>
      <property name="bindingName">Port</property>
      <property name="port">1299</property>
      <property name="description">The listening socket for the Naming service</property>
      </bean>

      <bean class="org.jboss.services.binding.ServiceBindingMetadata">
      <property name="serviceName">jboss:service=Naming</property>
      <property name="bindingName">RmiPort</property>
      <property name="port">1098</property>
      <property name="description">Socket Naming service uses to receive RMI requests from client proxies</property>
      </bean>

      So I put 1098 for the <cargo.rmi.port> instead of the 1299...
      I think cargo.rmi.port might be badly named...

        Gliffy Diagrams

          Attachments

            Activity

            There are no comments yet on this issue.

              People

              • Assignee:
                savasalitokmen Savas Ali Tokmen
                Reporter:
                gribovalphilippe Griboval Philippe
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: