Geronimo
  1. Geronimo
  2. GERONIMO-3546

sharedlib config should not start rmi-naming when used with offline deployer

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0.2, 2.1
    • Fix Version/s: 2.0.3, 2.1
    • Component/s: dependencies, usability
    • Security Level: public (Regular issues)
    • Labels:
      None
    • Environment:

      G 2.0.2 tomcat on WinXP

    • Patch Info:
      Patch Available

      Description

      sharedlib config has a dependency on rmi-naming. If a configuration that depends on sharedlib is to be deployed using offline deployer (see GERONIMO-3544), the required changes will result in rmi-naming config getting started during deployment which will result in bind exception while using multiple server instances. See GERONIMO-3481. Since sharedlib only requires ServerInfo gbean which is part of j2ee-system config, it shouldn't harm making the sharedlib depend on j2ee-system instead of rmi-naming.

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Vamsavardhana Reddy
              Reporter:
              Vamsavardhana Reddy
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development