[GERONIMO-3546] sharedlib config should not start rmi-naming when used with offline deployer

• Type: Bug
• Status: Closed
• Priority: 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)

Environment

G 2.0.2 tomcat on WinXP

• Patch Info: Patch Available
• Assignee: Vamsavardhana Reddy
• Reporter: Vamsavardhana Reddy
• Created: 23/Oct/07 14:02
• Updated: 23/Jul/08 20:52
• Resolved: 24/Oct/07 21:00

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

• blocks: GERONIMO-3544 Offline deployer busted when adding sharedlib reference into offline-deployer-config.xml
• relates to: GERONIMO-3481 Offline deployer throws BIND Exception when port 1099 is in use