[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-872) Unable to call EJB Remotely
Carlo de Wolf (JIRA)
jira-events at lists.jboss.org
Tue Sep 7 07:18:54 EDT 2010
[ https://jira.jboss.org/browse/EJBTHREE-872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlo de Wolf resolved EJBTHREE-872.
------------------------------------
Resolution: Out of Date
This issue is reported against a version which is no longer maintained,
which means that it will not receive a fix. As a result we are closing
this bug.
If you can reproduce this bug against a currently maintained version of
JBoss EJB 3 please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
> Unable to call EJB Remotely
> ---------------------------
>
> Key: EJBTHREE-872
> URL: https://jira.jboss.org/browse/EJBTHREE-872
> Project: EJB 3.0
> Issue Type: Bug
> Components: EJB3 Extensions
> Affects Versions: EJB 3.0 RC9 - FD
> Environment: two separate, non clustered jbosses
> Reporter: Henning Vogt
> Fix For: Branch_4_2
>
>
> See also the linked bug for detailed descripton.
> Calling a remote SLSB does not work, if the equally named SLSB is deployed on the calling JBoss.
> See also:
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96098
> and
> http://jira.jboss.com/jira/browse/EJBTHREE-823
> and numerous other topics on this.
> In my opinion, ther should be an easier way to do this, instead of writing your own interceptor, patching JBoss or the like.
> Also, in a non clustered environment, if you give a hostname to the InitialContext(), you should get the remote server session beans,
> regardless of possibly locally deployed equally named stateless sessionbeans.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list