You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2007/10/23 19:17:50 UTC

[jira] Commented: (GERONIMO-3546) sharedlib config should depend on j2ee-system instead of rmi-naming

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

David Jencks commented on GERONIMO-3546:
----------------------------------------

I ithink this will cause problems

- I think people will expect spec classes to be available in shared/lib and will be surprised by NCDFE otherwise
- to fix the offline deployer situation we may need to make the reference to serverInfo an optional single valued dependency so it can pick up the offline deployer's serverInfo

I think making all the parents <import>classes</import> is worth a try as an alternate fix.

> sharedlib config should depend on j2ee-system instead of rmi-naming
> -------------------------------------------------------------------
>
>                 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.