David,
It's not OpenEJB specific. We use the same properties to configure a JKS
public certificate in JBoss too.
> System.setProperty("javax.net.ssl.trustStoreType", "JKS");
> System.setProperty("javax.net.ssl.trustStore", "the path to the JKS
> file");
> System.setProperty("sun.security.ssl.allowUnsafeRenegotiation", "true");
>
I tried
> SystemInstance.get().setProperty("javax.net.ssl.trustStoreType", "JKS",
> true);
> SystemInstance.get().setProperty("javax.net.ssl.trustStore", "the path to
> the JKS file", true);
> SystemInstance.get().setProperty("sun.security.ssl.allowUnsafeRenegotiation",
> "true", true);
>
Thinking about what you said, I tried the "true" there because the
SystemInstance code apparently set the System.setProperties too. Didn't work
either.
The architect says that everything should stay in one VM. I actually agree
with him, since the change that we'd have to make would be enormous (I tried
and got a lot of problems along the way... very VERY weird problems - we
have a Mail object that it's returned from a Session. The client that uses
this Session gets this Mail object null and I don't know why, since there's
no Exception). The architecture would have to change too much, so I guess
that we're not in a very nice situation in this migration.
I'm running out of ideas :-|
Thanks in advance,
Regards,
Andre.
--
View this message in context:
http://openejb.979440.n4.nabble.com/OpenEJB-s-Context-doesn-t-support-bind-rebind-and-unbind-tp3580780p3616780.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
