Sun Java System Instant Messaging - Does SUN IM support XEP-0106 ?

We had a custom encoding in previous releases : so using '@' will work, but it wont be interoperable over s2s or with clients.

With u1 patch to R5 release, we support a server (and client) side flag to support using xep 106 compliant encoding.

If server is running in xep 106 mode, it will do data migration on the fly.

With this, existing customers who want to continue with current encoding can do so.

But if they want to use third party xep 106 compliant clients or want to enable s2s to other xmpp implementations (both open federation and whitelists supported) , setting to xep106 encoding will be necessary at im server & client.

Regards,

Mridul

MridulMa at 2007-7-10 14:42:44 >

I am really not sure of jwchat supporting xep106 (another customer indicated it does not).

But assuming it does (or you get it working), you will need to set 'iim_server.jid.encoding.compat' to false in iim.conf in R5 update 1 (when it is released) to support this.

If this is enabled, sun's im client should also be modified to support it (need to add org.netbeans.lib.collab.xmpp.JIDUtil.Provider=org.netbeans.lib.collab.xmpp.util.XEP106JIDUtil as an environment property in the jnlp).

There is no change required for the gateway.

Please do note that when compat mode is false, server does on the fly data migration to new format which is not reversible to older format.

Regards,

Mridul

MridulMa at 2007-7-10 14:42:44 >