You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org> on 2007/10/23 16:03:50 UTC
[jira] Created: (GERONIMO-3546) sharedlib config should depend on
j2ee-system instead of rmi-naming
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.
[jira] Commented: (GERONIMO-3546) sharedlib config should depend on
j2ee-system instead of rmi-naming
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Reopened: (GERONIMO-3546) sharedlib config should depend on
j2ee-system instead of rmi-naming
Posted by "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 reopened GERONIMO-3546:
-------------------------------------------
> 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.
[jira] Commented: (GERONIMO-3546) sharedlib config should not start
rmi-naming when used with offline deployer
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMO-3546) sharedlib config should not start
rmi-naming when used with offline deployer
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537243 ]
Vamsavardhana Reddy commented on GERONIMO-3546:
-----------------------------------------------
Rev 587806: Replacing rmi-naming dependency with j2ee-system resulted in NCDEF's for spec classes. Reinstated the rmi-naming dependency with <import>classes</import>
> 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.
[jira] Updated: (GERONIMO-3546) sharedlib config should not start
rmi-naming when used with offline deployer
Posted by "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 updated GERONIMO-3546:
------------------------------------------
Summary: sharedlib config should not start rmi-naming when used with offline deployer (was: sharedlib config should depend on j2ee-system instead of rmi-naming)
> 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.
[jira] Commented: (GERONIMO-3546) sharedlib config should depend on
j2ee-system instead of rmi-naming
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537110 ]
Vamsavardhana Reddy commented on GERONIMO-3546:
-----------------------------------------------
David,
how do I handle this part: "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"
> 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.
[jira] Commented: (GERONIMO-3546) sharedlib config should depend on
j2ee-system instead of rmi-naming
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537099 ]
Vamsavardhana Reddy commented on GERONIMO-3546:
-----------------------------------------------
When I change the sharedlib's dependency on rmi-naming to <import>classes</import>, I am getting the following build error:
[INFO] Packaging module configuration: C:\G\server\tags\2.0.2\configs\sharedlib\target\plan\plan.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Unable to resolve reference "ServerInfo"
in gbean org.apache.geronimo.configs/sharedlib/2.0.2/car?ServiceModule=org.a
pache.geronimo.configs/sharedlib/2.0.2/car,j2eeType=GBean,name=SharedLib
to a gbean matching the pattern [?j2eeType=GBean,name=ServerInfo#org.apache.
geronimo.system.serverinfo.ServerInfo]
due to: No matches for referencePatterns: [?j2eeType=GBean,name=ServerInfo#o
rg.apache.geronimo.system.serverinfo.ServerInfo]
> 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.
[jira] Closed: (GERONIMO-3546) sharedlib config should not start
rmi-naming when used with offline deployer
Posted by "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.
[jira] Updated: (GERONIMO-3546) sharedlib config should not start
rmi-naming when used with offline deployer
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bohn updated GERONIMO-3546:
-------------------------------
Affects Version/s: (was: 2.0.x)
2.0.2
Fix Version/s: (was: 2.0.x)
2.0.3
> 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.2, 2.1
> Environment: G 2.0.2 tomcat on WinXP
> Reporter: Vamsavardhana Reddy
> Assignee: Vamsavardhana Reddy
> Priority: Minor
> Fix For: 2.0.3, 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.
[jira] Closed: (GERONIMO-3546) sharedlib config should depend on
j2ee-system instead of rmi-naming
Posted by "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: 587515
> 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.
[jira] Commented: (GERONIMO-3546) sharedlib config should not start
rmi-naming when used with offline deployer
Posted by "Aman Nanner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537433 ]
Aman Nanner commented on GERONIMO-3546:
---------------------------------------
Ok, I'd like to test this out, but I'm suddenly getting this build error:
{code}
[exec] Downloading: file://D:\g20\g\repository//castor/castor/0.9.9.0-pre/castor-0.9.9.0-pre.pom
[exec] [WARNING] Unable to get resource 'castor:castor:pom:0.9.9.0-pre' from repository module-local (file://D:\g20
\g\repository/)
[exec] Downloading: http://download.java.net/maven/1//castor/poms/castor-0.9.9.0-pre.pom
[exec] [WARNING] Unable to get resource 'castor:castor:pom:0.9.9.0-pre' from repository java.net (http://download.j
ava.net/maven/1/)
[exec] Downloading: http://people.apache.org/repo/m2-incubating-repository//castor/castor/0.9.9.0-pre/castor-0.9.9.
0-pre.pom
[exec] [WARNING] Unable to get resource 'castor:castor:pom:0.9.9.0-pre' from repository apache-incubator (http://pe
ople.apache.org/repo/m2-incubating-repository/)
[exec] Downloading: http://repo1.maven.org/maven2/castor/castor/0.9.9.0-pre/castor-0.9.9.0-pre.pom
[exec] [WARNING] Unable to get resource 'castor:castor:pom:0.9.9.0-pre' from repository central (http://repo1.maven
.org/maven2)
[exec] Downloading: file://D:\g20\g\repository//castor/castor/0.9.9.0-pre/castor-0.9.9.0-pre.jar
[exec] [WARNING] Unable to get resource 'castor:castor:jar:0.9.9.0-pre' from repository module-local (file://D:\g20
\g\repository/)
[exec] Downloading: http://download.java.net/maven/1//castor/jars/castor-0.9.9.0-pre.jar
[exec] [WARNING] Unable to get resource 'castor:castor:jar:0.9.9.0-pre' from repository java.net (http://download.j
ava.net/maven/1/)
[exec] Downloading: http://people.apache.org/repo/m2-incubating-repository//castor/castor/0.9.9.0-pre/castor-0.9.9.
0-pre.jar
[exec] [WARNING] Unable to get resource 'castor:castor:jar:0.9.9.0-pre' from repository apache-incubator (http://pe
ople.apache.org/repo/m2-incubating-repository/)
[exec] Downloading: http://repo1.maven.org/maven2/castor/castor/0.9.9.0-pre/castor-0.9.9.0-pre.jar
[exec] [WARNING] Unable to get resource 'castor:castor:jar:0.9.9.0-pre' from repository central (http://repo1.maven
.org/maven2)
[exec] [INFO] ------------------------------------------------------------------------
[exec] [ERROR] BUILD ERROR
[exec] [INFO] ------------------------------------------------------------------------
[exec] [INFO] Failed to resolve artifact.
[exec] Missing:
[exec] ----------
[exec] 1) castor:castor:jar:0.9.9.0-pre
[exec] Try downloading the file manually from the project website.
[exec] Then, install it using the command:
[exec] mvn install:install-file -DgroupId=castor -DartifactId=castor \
[exec] -Dversion=0.9.9.0-pre -Dpackaging=jar -Dfile=/path/to/file
[exec] Path to dependency:
[exec] 1) org.apache.geronimo:repository:jar:2.0.2
[exec] 2) org.codehaus.mojo.jspc:jspc-maven-plugin:jar:2.0-alpha-1-20070806
[exec] 3) org.codehaus.mojo.groovy:groovy-mojo-support:jar:1.0-alpha-3
[exec] 4) org.codehaus.mojo.groovy:groovy-mojo-common:jar:1.0-alpha-3
[exec] 5) groovy:groovy-all:jar:1.0
[exec] 6) openejb:openejb-loader:jar:1.0
[exec] 7) openejb:openejb-core:jar:1.0
[exec] 8) castor:castor:jar:0.9.9.0-pre
[exec] ----------
[exec] 1 required artifact is missing.
[exec] for artifact:
[exec] org.apache.geronimo:repository:jar:2.0.2
[exec] from the specified remote repositories:
[exec] central (http://repo1.maven.org/maven2),
[exec] java.net (http://download.java.net/maven/1/),
[exec] apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
[exec] apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
[exec] codehaus-snapshots (http://snapshots.repository.codehaus.org),
[exec] apache-incubator (http://people.apache.org/repo/m2-incubating-repository/),
[exec] module-local (file://D:\g20\g\repository/)
{code}
Is this because the repository servers are down? Or would this indicate some kind of build corruption?
> 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.