The new stuff would be used when the client is trying to get at the JMX bus through a firewall. For example ..
Swing Client -> firewall -> internet -> firewall -> jboss By default al JNDI/EJB go over RMI on port 4444. In order for the above to work, the client firewall would have to allow RMI calls to go through and on the jboss firewall side it would have to forward port 4444 through to jboss. The new invokers wrap up the RMI call into http. Most firewalls allow http access and if the client firewall is a proxy firewall it will still work. On the server side most likely the http port is open to serve web pages so a servlet receives the response and sends it into the JMX bus. On Thu, 2002-08-29 at 00:12, Steve Knight wrote: > Hi, > > Can someone please explain to me in more detail the new HTTP to JMX Invoker > for RMI/HTTP for the JNDI service as well as > EJBs. > > > Thanks > > > ------------------------------------------------------- > This sf.net email is sponsored by: Jabber - The world's fastest growing > real-time communications platform! Don't just IM. Build it in! > http://www.jabber.com/osdn/xim > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
