-
1. Re: JBoss 3.2.1, RMI over HTTP
didi1976 Nov 27, 2003 9:36 AM (in response to realise)Hi,
try specifying a invoker-proxy-binding. I did not check the config below but we use an own invoker which uses https and that is the way we specified it there. You can set the invoker per EJB in you jboss.xml. In our case it is an stateful session bean which does the work.
jboss.xml:
...
<ejb-name>UserSessionBean</ejb-name>
<jndi-name>UserSessionBean</jndi-name>
<invoker-bindings>
<invoker-proxy-binding-name>http</invoker-proxy-binding-name>
<jndi-name>UserSessionBean</jndi-name>
</invoker-bindings>
...
<invoker-proxy-bindings>
<invoker-proxy-binding>
http
<invoker-mbean>jboss:service=invoker,type=http</invoker-mbean>
<proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory>
<proxy-factory-config>
<client-interceptors>
org.jboss.proxy.ejb.HomeInterceptor
org.jboss.proxy.SecurityInterceptor
org.jboss.proxy.TransactionInterceptor
org.jboss.invocation.InvokerInterceptor
org.jboss.proxy.ejb.StatefulSessionInterceptor
org.jboss.proxy.SecurityInterceptor
org.jboss.proxy.TransactionInterceptor
org.jboss.invocation.InvokerInterceptor
</client-interceptors>
</proxy-factory-config>
</invoker-proxy-binding>
</invoker-proxy-bindings>
...
Hope that helps.
Didi -
2. Re: JBoss 3.2.1, RMI over HTTP
realise Dec 8, 2003 9:42 AM (in response to realise)Many Many Thanks for this!
It turns out that we don't have to make *any* changes to the JBoss configuration whatsoever...
This makes sense - if you had a large cluster of JBoss services, feeding multiple clients, then you ought not to be "hobbling" JBoss to work RMI in any particular way...
The secret is to get your Beans to tell JBoss how to communicate with them (as in your example) and tell your web server to invoke all JNDI calls over the JNDIFactory servlet.
I imaging you might have to explicity state your invoker addresses in http-invoker.war, but we have found in practice that each installation can build this URL on its own.
Once again, many thanks.
Regards,
Seumas