Hello, Thanks so much for your email. My Jira ID is "knaderi". I am glad that you have a practical solution to get this done as a patch for 3.0. Please let me know what steps I should take to facilitate this. Should I attached our implementation to the new Faeture in Jira or what you have in mind is to have us implement this and contribute it to the code base?
Best Regards Kazem Naderi -----Original Message----- From: David Blevins [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2008 12:16 PM To: [email protected]; Kazem Naderi Subject: Re: SSL works for us, do you support it? Importance: High Hi Kazem, We'd absolutely love this feature and I don't see any reason we couldn't get it in. In fact, we're trying to get our 3.0 release out the door now and could include it in that if you're able to get a patch against trunk/openejb3 to us. I've opened a Jira issue where you can attach it: http://issues.apache.org/jira/browse/OPENEJB-785 We can add a flag to the standard set of properties a server service can set, setup a second ejbd service on a different port, then add a new protocol prefix on the client side that will set the SSLSocketConnectionFactory automatically. Also, let me know your Jira id and I'll add you to the openejb- contributors jira permissions group. -David On Mar 26, 2008, at 5:21 PM, Kazem Naderi wrote: > 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. > >
