Hello, For our client-server application we needed to use end to end SSL for ejb(using openejb) socket connections. I understand that this is not currently supported for ejb. This made us to do the following to get it working for us: 1. On the client side we subclassed your SocketConnectionFactory.java from your distributed source package to a new class called SSLSocketConnectionFactory. In this new class we used SSLScoket instead of Socket. Then we use ConnectionManager.setfactory() method to use this new factory class instead. 2. On the server side we needed to basically modify your serviceDeamon.java and use SSLServerSocket instead of ServerSocket. Then we compiled the new ServiceDeamon.java and updated your openeib-server.jar file with the new ServiceDeamon.class file. I understand that though the changes we made works for us they are not deliverable to Apache because they do not give an option to the user to configure using SSL VS the non secure connection. My question is, are you going to add this feature to your next release(supporting SSL)? We really do not want to fall out of synch with your releases and be worried about updating your release with our internal custom implementation. Is there anything we can do to have this implemented in the next release? Do you want me to send you a copy of our implementation so you can continue expanding on that for your next release? I appreciate your response on this. Best Regards ________________________________
Kazem Naderi Architect ACL Services Ltd. 1550 Alberni Street | Vancouver | BC | V6G 1A5 Tel: 604 669 4225 | Direct: 604 646 4218 | Fax: 604 692 1396 Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> | Web: www.acl.com <http://www.acl.com/> Register Now at www.aclconnections.com <http://www.aclconnections.com/> for the ACL Global User Conference - April 15-17, 2007 ________________________________ The contents of this email are confidential and are for the intended recipient(s) named above only. If you are not the intended recipient, any copying, distribution or use of this email is prohibited. If you have received this email in error, please notify the sender and delete the email.
