[jira] Closed: (GERONIMO-3546) sharedlib config should not start rmi-naming when used with offline deployer

["Vamsavardhana Reddy (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GERONIMO-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vamsavardhana Reddy closed GERONIMO-3546.
-----------------------------------------

    Resolution: Fixed

Completed: At revision: 588019  

 o Thanks to David Jencks for suggesting a better solution than the one I had cooked originally.
 o Reverse rev 587515 and 587806
 o Change the dependency scope of rmi-naming to runtime i.e. <import>classes</import>
 o Make SharedLib use SingleElementCollection for ServerInfo


> sharedlib config should not start rmi-naming when used with offline deployer
> ----------------------------------------------------------------------------
>
>                 Key: GERONIMO-3546
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3546
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: dependencies, usability
>    Affects Versions: 2.0.x, 2.1
>         Environment: G 2.0.2 tomcat on WinXP
>            Reporter: Vamsavardhana Reddy
>            Assignee: Vamsavardhana Reddy
>            Priority: Minor
>             Fix For: 2.0.x, 2.1
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.