Marcel Romijn

Hi Zhang Ze, Thanks for sending me the link to the Contributor License Agreement. I'll have to run it through my manager and optionally the legal department. If all lights turn green, I will e-mail the signed form. Kind regards, Marcel Romijn

Hello Zhang Ze, I understand contributions can only be made by IBM :-) If the repository of JTOpen would be Git, I could present a PR with the changes we would need. But since JTOpen is in a SVN repository, I don't know how to present our changes to a contributor. Maybe by providing a patch somehow? Kind regards, Marcel Romijn

Hello, Our (hopefully temporary) solution now is to clone the JTOpen sources, make the changes we need and use that in our product. In alignment with the license, we will make the changed sources public when we release the product that uses them. Maybe we will make the changed sources public before our product is released. But ultimately, having these changes in the original JTOpen code base would be more convenient and efficient. Regards, Marcel Romijn

Provide a custom 'SSLSocketFactory'

Hello JTOpen team, I'm replying to this (closed) issue because we are facing a similar situation. Our (development) IBM i machines have certificates that are signed by a CA that is internal to the company and our customers may have the same situation. This means that a secure connection with JTOpen will not work by default. The alternative would be to provide the command-line System Properties to point to a trust store. However, due to technical reasons, we would like to avoid that. We had a look...