geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vamsavardhana Reddy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-3546) sharedlib config should not start rmi-naming when used with offline deployer
Date Thu, 25 Oct 2007 07:43:50 GMT

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

Vamsavardhana Reddy commented on GERONIMO-3546:
-----------------------------------------------

In my local repository, I have castor-0.9.9.jar only.  From where is it picking that version
number "0.9.9.0-pre"?

> 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.


Mime
View raw message