Bordet, Simone
2002-02-11 14:37:15 UTC
Hi,
I committed the revisited RMI adaptor, hehe.
As a result CVS may be a little unstable for few days (only the part of the RMIAdaptor, though), but I will fix everything for the release candidate.
BTW I propose future major release always follow the pattern of 2 beta releases, one RC then the final.
-------o--------
RMIAdaptor
This MBean allow clients to connect to the MBeanServer via RMI. Notice please that RMI is not a protocol, and here must be intended as "remote method invocation using Java". The underlying protocol can be anyone, and in fact 2 are supported: JRMP and IIOP.
JRMP is the Java Remote Method Protocol, and it's the default protocol for RMI.
IIOP is the Internet Inter Orb Protocol, and it's the CORBA default.
As you know, remote method invocation in Java can have JRMP or IIOP as protocols, and the remote invocation process is usually referred to, respectively, as "RMI" and "RMI over IIOP". "RMI" is a short for "RMI over JRMP".
So we have the RMI adaptor that is protocol independent, and support for remote notification listeners and filters.
-------o--------
IIOPAdaptor
This MBean is a subclass of the RMIAdaptor and handles IIOP specific operations.
-------o--------
JRMPAdaptor
This MBean is a subclass of the RMIAdaptor and handles JRMP specific operations. It supports export on a specific port and with custom socket factories.
It supports SSL, so it is possible to have a JRMPAdaptor over SSL for secure data transfer.
-------o--------
RMIConnector
This is the class that remote clients of MBeanServer must use to connect to the RMIAdaptor subclasses. It serves for both JRMP and IIOP adaptor. It is based on JNDI to lookup the adaptors, so be sure to configure it properly to find the adaptor's stub, either from the RMI naming or from the COS naming (for RMI and CORBA respectively).
Don't try to use directly the stub of the adaptors, unless you know what you're doing :), always use this class.
That's it for now.
Examples and docs will come soon.
Cheers
Simon
I committed the revisited RMI adaptor, hehe.
As a result CVS may be a little unstable for few days (only the part of the RMIAdaptor, though), but I will fix everything for the release candidate.
BTW I propose future major release always follow the pattern of 2 beta releases, one RC then the final.
-------o--------
RMIAdaptor
This MBean allow clients to connect to the MBeanServer via RMI. Notice please that RMI is not a protocol, and here must be intended as "remote method invocation using Java". The underlying protocol can be anyone, and in fact 2 are supported: JRMP and IIOP.
JRMP is the Java Remote Method Protocol, and it's the default protocol for RMI.
IIOP is the Internet Inter Orb Protocol, and it's the CORBA default.
As you know, remote method invocation in Java can have JRMP or IIOP as protocols, and the remote invocation process is usually referred to, respectively, as "RMI" and "RMI over IIOP". "RMI" is a short for "RMI over JRMP".
So we have the RMI adaptor that is protocol independent, and support for remote notification listeners and filters.
-------o--------
IIOPAdaptor
This MBean is a subclass of the RMIAdaptor and handles IIOP specific operations.
-------o--------
JRMPAdaptor
This MBean is a subclass of the RMIAdaptor and handles JRMP specific operations. It supports export on a specific port and with custom socket factories.
It supports SSL, so it is possible to have a JRMPAdaptor over SSL for secure data transfer.
-------o--------
RMIConnector
This is the class that remote clients of MBeanServer must use to connect to the RMIAdaptor subclasses. It serves for both JRMP and IIOP adaptor. It is based on JNDI to lookup the adaptors, so be sure to configure it properly to find the adaptor's stub, either from the RMI naming or from the COS naming (for RMI and CORBA respectively).
Don't try to use directly the stub of the adaptors, unless you know what you're doing :), always use this class.
That's it for now.
Examples and docs will come soon.
Cheers
Simon