Hello,
[...]
> I would suggest simply adding support for externalizing the
RMIServerSocketFactory
> and RMIClientSocketFactory from the
org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker
> class. Right now it exports itself in the start method:
>
> public void start() throws Exception
> {
> ...
> // Export CI
> UnicastRemoteObject.exportObject(this, rmiPort);
> ...
> }
>
> Change this to:
>
> RMIClientSocketFactory csf; // MetaData configurable
> RMIServerSocketFactory ssf;
> public void start() throws Exception
> {
> ...
> // Export CI
> UnicastRemoteObject.exportObject(this, rmiPort, csf, ssf);
> ...
> }
>
> and you have the ability to use SSL and a whole lot more.
>
[...]
I made the experiences, that it is not necessary to export every remote
object which SSL-sockets. so ist would be helpful setting a flag/tag in the
xml-deployment-file, which bean should use SSL-sockets.
Furthermore, you should consider having the posssibility, to give in a
global conf-file the passphrase for the keystore, where all ssl related keys
and certificates are stored.
so long...
Daniel
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
