Re: soap+ssl

Hi,

[please reply to the list]

> I'm using MX4j-3.0.2. I think it's the newest version at the moment. I have
> found a solution to my problem through giving server truststore information.
> Also I inserted the following code in the server class:
>
>     System.setProperty("javax.net.ssl.trustStore", "./etc/keystore");
>
>     System.setProperty("javax.net.ssl.trustStorePassword",
> "password");
>
>     System.setProperty("javax.net.ssl.keyStoreType", "jks");

Yes.

> But i don't know why the server side need the information about truststore
> either? As far as I know, such information would be used by client to
> authenticate server. The handshake seems to be used by server hierby to
> deploy the service too. Could you explain it?

The truststore is required as part of the SSL handshake. The JVM uses
a default truststore (jre/lib/security/cacerts) that contains the
certificates signed by CA roots. Of course, a self-signed certificate
such as the one you probably generated is not contained in cacerts,
and thus you need a custom truststore.

> Otherwise, this version of MX4J don't support passing OpenMBeans
> types(CompositeType, TabularType) via soap, do it?

No :( Support for OpenMBeans over soap is still to be implemented.

> Man need to write coresponding (de)serialization-factorys for these typs. do
> you have them?

No. If you're going to write them let's keep an open channel so that
they may be included in MX4J, if that's ok with you.

Simon
-- 
http://bordet.blogspot.com

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/