the way to resolve this problem is to specify jndi-name for every bean and invoker, e.g.:
<ejb-name>TestEjb</ejb-name>
<invoker-bindings>
<invoker>
<invoker-proxy-binding-name>stateless-rmi-invoker</invoker-proxy-binding-name>
<jndi-name>TestSessionBean</jndi-name>
</invoker>
<invoker> <invoker-proxy-binding-name>stateless-http-invoker</invoker-proxy-binding-name>
<jndi-name>http/TestSessionBean</jndi-name>
</invoker>
</invoker-bindings>
...
then your http client will lookup the bean under http/TestSessionBean. This works fine for me.
The only problem that I have is when the bean has a method which returns to the client a remote interface of another bean.
In this case, the remote interface is not http/AnotherBean, but AnotherBean - again rmi is used.
The JBoss docs say that ejb-ref must be used inside invoker element of jboss.xml, but the result is still the same.
Hope that this is helpfull.
Tsvetan
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
